Sometimes this breaks, so add a build to keep it working. Since sandbox enables a lot of options, it is a good board to use. The new config is created simply by copying the existing sandbox and turning off CMDLINE
Once we have tests for non-CMDLINE operation, this can be adjusted to run those tests. Create a new build which will be picked up by CI. Update the maintainer entry as well. Signed-off-by: Simon Glass <s...@chromium.org> --- Changes in v3: - Use #include in the defconfig - Fix 'Something' typo Changes in v2: - Create a new build instead of messing with CI MAINTAINERS | 1 + configs/sandbox_nocmdline_defconfig | 2 ++ 2 files changed, 3 insertions(+) create mode 100644 configs/sandbox_nocmdline_defconfig diff --git a/MAINTAINERS b/MAINTAINERS index df046192ea0..c7044220452 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -1544,6 +1544,7 @@ SANDBOX M: Simon Glass <s...@chromium.org> S: Maintained F: arch/sandbox/ +F: configs/sandbox* F: doc/arch/sandbox.rst F: drivers/*/*sandbox*.c F: include/dt-bindings/*/sandbox*.h diff --git a/configs/sandbox_nocmdline_defconfig b/configs/sandbox_nocmdline_defconfig new file mode 100644 index 00000000000..03173113fd5 --- /dev/null +++ b/configs/sandbox_nocmdline_defconfig @@ -0,0 +1,2 @@ +#include "sandbox_defconfig" +# CONFIG_CMDLINE is not set -- 2.43.0
