From: Arnd Bergmann <arnd@arndb.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
linux-serial@vger.kernel.org
Subject: Re: [PATCH 2/3 v2] tty: source all tty Kconfig files in one place
Date: Thu, 12 Mar 2020 09:18:47 +0100 [thread overview]
Message-ID: <CAK8P3a0LNFJ1srVAXrN6PKh9y9d4VXLz-NYRLsx5coF5uuS3_Q@mail.gmail.com> (raw)
In-Reply-To: <20200311225736.32147-3-rdunlap@infradead.org>
On Wed, Mar 11, 2020 at 11:57 PM Randy Dunlap <rdunlap@infradead.org> wrote:
>
> 'source' (include) all of the tty/*/Kconfig files from
> drivers/tty/Kconfig instead of from drivers/char/Kconfig.
> This consolidates them both in source code and in menu
> presentation to the user.
>
> Move hvc/Kconfig and serial/Kconfig 'source' lines into the
> if TTY/endif block and remove the if TTY/endif blocks from
> those 2 files.
>
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> Suggested-by: Jiri Slaby <jslaby@suse.com>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Jiri Slaby <jslaby@suse.com>
> Cc: linux-serial@vger.kernel.org
> ---
> v2: move hvc/Kconfig & serial/Kconfig lines and drop their if/endif blocks
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2020-03-12 8:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 22:57 [PATCH 0/3 v2] char/tty: clean up menus Randy Dunlap
2020-03-11 22:57 ` [PATCH 1/3 v2] char: group dev configs togther Randy Dunlap
2020-03-12 8:18 ` Arnd Bergmann
2020-03-11 22:57 ` [PATCH 2/3 v2] tty: source all tty Kconfig files in one place Randy Dunlap
2020-03-12 8:18 ` Arnd Bergmann [this message]
2020-03-11 22:57 ` [PATCH 3/3 v2] tty: reorganize tty & serial menus Randy Dunlap
2020-03-12 8:21 ` Arnd Bergmann
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=CAK8P3a0LNFJ1srVAXrN6PKh9y9d4VXLz-NYRLsx5coF5uuS3_Q@mail.gmail.com \
--to=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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 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).