From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: include architecture Kconfig files from top-level Kconfig
Date: Thu, 5 Jul 2018 14:47:19 +0900 [thread overview]
Message-ID: <CAK7LNAS5md-Q3iyKNa4vraHWRa28E_RhuObJaxssBp2aWzrYDA@mail.gmail.com> (raw)
In-Reply-To: <20180702144711.22111-1-hch@lst.de>
Hi.
2018-07-02 23:47 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.
Basically, I am positive about this work.
As you have already noticed,
the UML breakage should be fixed.
If the reported problems are stretched out,
I think this is a nice cleanup.
Thanks.
> 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
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2018-07-05 5:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 14:47 include architecture Kconfig files from top-level Kconfig Christoph Hellwig
2018-07-02 14:47 ` [PATCH 1/5] kconfig: include common " Christoph Hellwig
2018-07-02 20:03 ` Randy Dunlap
2018-07-02 20:08 ` Randy Dunlap
2018-07-03 13:36 ` Christoph Hellwig
2018-07-03 16:11 ` Randy Dunlap
2018-07-05 5:38 ` Masahiro Yamada
2018-07-03 13:35 ` Christoph Hellwig
2018-07-02 20:41 ` Randy Dunlap
2018-07-02 20:50 ` Randy Dunlap
2018-07-05 6:04 ` Masahiro Yamada
2018-07-02 14:47 ` [PATCH 2/5] Kconfig: consolidate the "Kernel hacking menu" Christoph Hellwig
2018-07-02 20:28 ` Randy Dunlap
2018-07-05 5:40 ` Masahiro Yamada
2018-07-02 14:47 ` [PATCH 3/5] kconfig: include kernel/Kconfig.preempt from top-level Kconfig Christoph Hellwig
2018-07-02 22:02 ` [PATCH] Kconfig: menus: add PREEMPT options back Randy Dunlap
2018-07-02 14:47 ` [PATCH 4/5] kconfig: add a Memory Management options" menu Christoph Hellwig
2018-07-02 20:57 ` Randy Dunlap
2018-07-02 14:47 ` [PATCH 5/5] kconfig: move the "Executable file formats" menu to fs/Kconfig.binfmt Christoph Hellwig
2018-07-02 20:58 ` Randy Dunlap
2018-07-02 21:17 ` [PATCH] arch/Kconfig: use a menu to reduce clutter Randy Dunlap
2018-07-03 13:39 ` Christoph Hellwig
2018-07-03 13:40 ` Christoph Hellwig
2018-07-05 5:47 ` Masahiro Yamada [this message]
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=CAK7LNAS5md-Q3iyKNa4vraHWRa28E_RhuObJaxssBp2aWzrYDA@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=hch@lst.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.