android-wireguard-module-builder, branch masterBuilder of WireGuard module for Android kernelshttps://git.zx2c4.com/android-wireguard-module-builder/atom/?h=master2021-05-06T17:56:23ZMay update2021-05-06T17:56:23ZNathan Chancellornathan@kernel.org2021-05-06T17:56:23Zurn:sha1:4fe26d9f23aec21bef253cac023f69657df7ee7f
Closes: #7
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
January update2021-01-05T02:23:01ZNathan Chancellornatechancellor@gmail.com2021-01-05T02:23:01Zurn:sha1:73b44e0227f477526be62ff512f302685e5c3076
Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
November update2020-11-06T04:18:25ZNathan Chancellornatechancellor@gmail.com2020-11-06T04:18:25Zurn:sha1:6b528b5bbd098016b1abf1d7003e6e32697d5618
Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
build-one.bash: override user's default branch name for temporary manifest repo2020-10-30T20:02:24ZNathan Chancellornatechancellor@gmail.com2020-10-30T19:57:32Zurn:sha1:0917b8287ca4f42ee9557045c3f65d989376898f
If a user has specified init.defaultBranch via git config, repo will
fail to properly init the temporary manifest repo.
$ ./build-one.bash ...
...
+ repo init -u ./manifest
Downloading Repo source from https://gerrit.googlesource.com/git-repo
repo: Updating release signing keys to keyset ver 2.3
Downloading manifest from ./manifest
fatal: couldn't find remote ref refs/heads/master
manifests:
fatal: couldn't find remote ref refs/heads/master
fatal: couldn't find remote ref refs/heads/master
manifests:
fatal: couldn't find remote ref refs/heads/master
fatal: cannot obtain manifest ./manifest
To fix this, force the branch to be named master, which aligns with
current repo expectations.
Link: https://gerrit.googlesource.com/git-repo/+/50a81de2bc9f2074d56c368f651cf9f50c8d8a87
Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
October update2020-10-07T07:02:08ZNathan Chancellornatechancellor@gmail.com2020-10-07T07:02:08Zurn:sha1:56a8581a2bad2ea0db0a0bccfe31e979ca41d6a6
Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
coral: use newer clang toolchain revision2020-09-15T12:18:28ZJason A. DonenfeldJason@zx2c4.com2020-09-15T12:06:16Zurn:sha1:f9a2cc98a5acc5a9cd16289d33f6095af15b5563
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
September update2020-09-15T06:02:41ZNathan Chancellornatechancellor@gmail.com2020-09-15T06:02:41Zurn:sha1:dce176b8a77ce7585b66391d32d4c4a2da73f3f6
Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
August update2020-08-04T02:33:42ZNathan Chancellornatechancellor@gmail.com2020-08-04T02:33:42Zurn:sha1:7d5999052d55cde1a1dc4d17a666b90b2a193342
Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
July update2020-07-07T03:30:01ZNathan Chancellornatechancellor@gmail.com2020-07-07T03:30:01Zurn:sha1:21be9850c92e36ea969bdb4f864cfcc839e6f227
Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>
kernels: wahoo: apply a patch to fix the build2020-06-02T21:46:50ZNathan Chancellornatechancellor@gmail.com2020-06-02T21:46:50Zurn:sha1:4e217ddb576884a70fa3cdc08dc96da02dcddb37
We need this patch after upstream stable commit 78d19b437554 ("kbuild:
fix single target build for external module") was merged via 4.4.210 in
the June security update. prepare is now called when building an
external module, which calls vdso_prepare, which then calls prepare0,
which is only defined when KBUILD_EXTMOD is set.
This is not a problem for upstream stable because commit
a66649dab350 ("arm64: fix vdso-offsets.h dependency") is not applied
there; it is only applied in the Wahoo tree as part of a series of vDSO
commits they added.
Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>