From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Michal Simek <monstr@monstr.eu>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Richard Weinberger <richard@nod.at>,
Randy Dunlap <rdunlap@infradead.org>,
linux-um@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch@lists.infradead.org, Ley Foon Tan <lftan@altera.com>
Subject: Re: include architecture Kconfig files from top-level Kconfig v3
Date: Wed, 25 Jul 2018 13:30:24 +0900 [thread overview]
Message-ID: <CAK7LNARP2HZ8GdsAU8h_b04jLWbvFXTWqiVt2hpE0vJbjP82ZA@mail.gmail.com> (raw)
In-Reply-To: <20180724175646.3621-1-hch@lst.de>
2018-07-25 2:56 GMT+09:00 Christoph Hellwig <hch@lst.de>:
> Hi Masahiro,
>
> what do you think about the series below, which moves the includes
> of all the architecture independ Kconfig files to the top-level
> Kconfig instead of duplicating the includes in all architectures?
>
> Note that this only handles the low-hanging fruite, there are a lot
> of other bits that should probably be cleaned up to be common,
> but those will be not entirely trivial.
>
> Changes since v2:
> - fix the missing sh conversion
> - handle the lack of CONFIG_SWAP support in microblaze and nios2 properly
>
> Changes since v1:
> - add back a remove source statement from arch/arm/Kconfig
> - various fixes from Randy
> - various UML patches to be able to use the common Kconfig
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
This version passed my tests.
Could you check the difference of CONFIG_PREEMPT_COUNT, please?
For alpha, hexagon, um,
CONFIG_PREEMPT_COUNT was previously never enabled
because kernel/Kconfig.preempt was not included.
Now, CONFIG_PREEMPT_COUNT can be enabled
if it is select'ed by someone.
I guess this change will be OK, but
I'd like you and Randy to double-check it just in case.
--
Best Regards
Masahiro Yamada
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2018-07-25 4:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 17:56 include architecture Kconfig files from top-level Kconfig v3 Christoph Hellwig
2018-07-24 17:56 ` [PATCH 01/10] um: stop abusing KBUILD_KCONFIG Christoph Hellwig
2018-07-24 17:56 ` [PATCH 02/10] um: cleanup Kconfig files Christoph Hellwig
2018-07-24 17:56 ` [PATCH 03/10] um: create a proper drivers Kconfig Christoph Hellwig
2018-07-24 17:56 ` [PATCH 04/10] kconfig: remove duplicate SWAP symbol defintions Christoph Hellwig
2018-07-24 17:56 ` [PATCH 05/10] kconfig: include common Kconfig files from top-level Kconfig Christoph Hellwig
2018-07-24 17:56 ` [PATCH 06/10] Kconfig: consolidate the "Kernel hacking" menu Christoph Hellwig
2018-07-24 17:56 ` [PATCH 07/10] kconfig: include kernel/Kconfig.preempt from init/Kconfig Christoph Hellwig
2018-07-24 17:56 ` [PATCH 08/10] kconfig: use a menu in arch/Kconfig to reduce clutter Christoph Hellwig
2018-07-24 17:56 ` [PATCH 09/10] kconfig: move the "Executable file formats" menu to fs/Kconfig.binfmt Christoph Hellwig
2018-07-24 17:56 ` [PATCH 10/10] kconfig: add a Memory Management options" menu Christoph Hellwig
2018-07-25 4:30 ` Masahiro Yamada [this message]
2018-07-26 17:21 ` include architecture Kconfig files from top-level Kconfig v3 Christoph Hellwig
2018-07-27 1:32 ` Masahiro Yamada
2018-07-27 7:48 ` Christoph Hellwig
2018-07-28 0:50 ` Masahiro Yamada
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=CAK7LNARP2HZ8GdsAU8h_b04jLWbvFXTWqiVt2hpE0vJbjP82ZA@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=hch@lst.de \
--cc=lftan@altera.com \
--cc=linux-arch@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=monstr@monstr.eu \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
/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;
as well as URLs for NNTP newsgroup(s).