From: Christoph Hellwig <hch@lst.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Christoph Hellwig <hch@lst.de>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/Kconfig: use a menu to reduce clutter
Date: Tue, 3 Jul 2018 15:39:59 +0200 [thread overview]
Message-ID: <20180703133959.GC15589@lst.de> (raw)
In-Reply-To: <6ba546f8-42bd-4400-131f-bb389812cb56@infradead.org>
Thanks, folded into the original preempt patch.
next prev parent reply other threads:[~2018-07-03 13:39 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 [this message]
2018-07-03 13:40 ` Christoph Hellwig
2018-07-05 5:47 ` include architecture Kconfig files from top-level Kconfig 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=20180703133959.GC15589@lst.de \
--to=hch@lst.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=yamada.masahiro@socionext.com \
/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