| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Use the latest available revision and disable ANDROID_BINDER_IPC - as of
now, it's no longer possible to compile in both C and Rust versions at
the same time.
|
| | |
|
| |
|
|
| |
Now that Rust Binder has been merged into the tree, we can enable it.
|
| |
|
|
|
|
|
|
|
| |
A config bisection between our LTS and Android configs have pointed to
the SERIAL_8250_RUNTIME_UARTS option determining whether the kernel
will hang during boot in qemu.
Set SERIAL_8250_RUNTIME_UARTS=4 on our Android kernels to make them
bootable.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit d341bdbd6837aa0214ee9dfd1c3ddfc58c2a0c9c.
The bump of CONFIG_FRAME_WARN was done for Android 5.10 with the hope
to get rid of the -Wframe-larger-than errors that were hit when
KASAN_STACK && CC_IS_CLANG were set. Unfortunately this didn't fix the
build as the stack instrumentation when using clang is broken and the
errors were hit again as we can't predict the increase of the stack. The
fix is to disable CONFIG_WERROR which now is done because we just bumped
the Android 5.10 kernel config (which contains CONFIG_WERROR=y) and the
kernel config tweak that disables CONFIG_WERROR now does its job
(see dashboard/config/linux/bits/base.yml).
Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
|
| |
|
|
|
| |
We are not able to build Android 5.10 because of that warning for
already more than 100 days. Just in case bump it for all Androids.
|
| |
|
|
|
| |
See discussion here about why this affected android 5.4:
https://github.com/google/syzkaller/pull/3518#issuecomment-1313533618
|
| |
|
|
| |
regenerate configs
|
| |
|
|
|
|
|
| |
"cgroup_disable=pressure cgroup.memory=nokmem" would affect kernel behaviour.
Suggested-by: Dmitry Vyukov <dvyukov@google.com>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Android
KASAN_STACK_ENABLE was renamed to KASAN_STACK in kernel version v5.11.
This change was also back-ported to android12-5.10, so we need to
provide support for that here too or else `make configs` will complain
that KASAN_STACK_ENABLE is not enabled.
Signed-off-by: Lee Jones <lee.jones@linaro.org>
|
|
|
ESD_FS/INCREMENTAL_FS were supposed to be enabled in full config only,
but they were enabled only in baseline config.
Split chromeos.yml to chromeos.yml and chromeos-subsystems.yml
to avoid this mistake in future and the need to write [-baseline].
Also enabled UBS_CONFIG_FS as it seems to be enabled on real devices.
Do the same for Android.
|
