[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNAS+XHGete9u2SV7fTj3HpROQmzfuJhV8tXW_xXkoPOYvg@mail.gmail.com>
Date: Tue, 7 Jan 2020 03:04:28 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: John Garry <john.garry@...wei.com>
Cc: Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Anders Roxell <anders.roxell@...aro.org>
Subject: Re: [PATCH] merge_config.sh: Add option for allmodconfig
On Mon, Jan 6, 2020 at 6:18 PM John Garry <john.garry@...wei.com> wrote:
>
> 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.
I do not understand why you need to use merge_config.sh
for this purpose.
KCONFIG_ALLCONFIG=<path-to-your-config-fragment> make allmodconfig
should work.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists