From: John Garry <john.garry@huawei.com>
To: <masahiroy@kernel.org>
Cc: <linux-kbuild@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<anders.roxell@linaro.org>
Subject: Re: [PATCH] merge_config.sh: Add option for allmodconfig
Date: Mon, 6 Jan 2020 09:18:47 +0000 [thread overview]
Message-ID: <7e769634-eb22-5827-e2d8-df68134056c0@huawei.com> (raw)
In-Reply-To: <1575979754-184896-1-git-send-email-john.garry@huawei.com>
On 10/12/2019 12:09, John Garry wrote:
Hi Masahiro,
Could you please consider this patch?
Thanks,
John
> Recently there has been some work in reporting and fixing bugs in booting
> an allmodconfig kernel - here are a few examples:
>
> https://lore.kernel.org/linux-edac/304df85b-8b56-b77e-1a11-aa23769f2e7c@huawei.com/T/#t
> https://lore.kernel.org/linux-ide/bdf02e03-86a1-3d35-2908-28187f504495@huawei.com/T/#t
> https://lore.kernel.org/netdev/CADYN=9LCPfbpwdTWKw03B22-y3Text=RWXW7XP7wJBHYsMOgrA@mail.gmail.com/
> https://sourceforge.net/p/openipmi/mailman/message/36871567/
>
> If we want to boot an allmodconfig kernel we may still want to force some
> loadable modules built-in, like UART drivers. Or just still turn off some
> configs.
>
> So add an option to add add fragments to an allmodconfig kernel.
>
> Signed-off-by: John Garry <john.garry@huawei.com>
>
> diff --git a/scripts/kconfig/merge_config.sh b/scripts/kconfig/merge_config.sh
> index 63c8565206a4..01697fb6dfbe 100755
> --- a/scripts/kconfig/merge_config.sh
> +++ b/scripts/kconfig/merge_config.sh
> @@ -23,6 +23,7 @@ clean_up() {
> usage() {
> echo "Usage: $0 [OPTIONS] [CONFIG [...]]"
> echo " -h display this help text"
> + echo " -a use allmodconfig instead of alldefconfig"
> echo " -m only merge the fragments, do not execute the make command"
> echo " -n use allnoconfig instead of alldefconfig"
> echo " -r list redundant entries when merging fragments"
> @@ -41,6 +42,11 @@ CONFIG_PREFIX=${CONFIG_-CONFIG_}
>
> while true; do
> case $1 in
> + "-a")
> + ALLTARGET=allmodconfig
> + shift
> + continue
> + ;;
> "-n")
> ALLTARGET=allnoconfig
> shift
> @@ -171,6 +177,7 @@ fi
>
> # Use the merged file as the starting point for:
> # alldefconfig: Fills in any missing symbols with Kconfig default
> +# allmodconfig: Fills in any missing symbols with =m when loadable
> # allnoconfig: Fills in any missing symbols with # CONFIG_* is not set
> make KCONFIG_ALLCONFIG=$TMP_FILE $OUTPUT_ARG $ALLTARGET
>
>
next prev parent reply other threads:[~2020-01-06 9:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 12:09 John Garry
2020-01-06 9:18 ` John Garry [this message]
2020-01-06 18:04 ` Masahiro Yamada
2020-01-07 9:19 ` John Garry
2020-01-09 16:21 ` Masahiro Yamada
2020-01-09 16:23 ` John Garry
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e769634-eb22-5827-e2d8-df68134056c0@huawei.com \
--to=john.garry@huawei.com \
--cc=anders.roxell@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®