From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>
Cc: Jiri Slaby <jslaby@suse.com>,
linux-serial@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
uclinux-h8-devel@lists.sourceforge.jp, linux-sh@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 0/5] tty: serial: sh-sci: Hide driver specific config questions
Date: Thu, 30 Nov 2017 14:11:57 +0100 [thread overview]
Message-ID: <1512047522-16312-1-git-send-email-geert+renesas@glider.be> (raw)
Hi Greg, Simon, Magnus, Sato-san, Rich,
The Renesas (H)SCI(F) driver has several driver-specific config options.
This may confuse users, and leads to inefficient testing and development.
E.g. recently a regression was introduced in SCIF DMA support, and
someone didn't see early con output, both due to the relevant options
being accidentally disabled.
This patch series is an attempt to stop bothering (H)SCI(F) users with
several config questions, while providing sensible defaults for these
options, based on the target platform. The defaults can still be
overridden if CONFIG_EXPERT is enabled.
The last patch updates shmobile_defconfig to take into account the
defaults. It is marked RFC, as it depends on the first 4 patches to be
effective, and to avoid feature regressions.
Thanks for your comments!
Geert Uytterhoeven (5):
tty: serial: sh-sci: Hide number of ports config question
tty: serial: sh-sci: Hide serial console config question
tty: serial: sh-sci: Hide earlycon config question
tty: serial: sh-sci: Hide DMA config question
[RFC] ARM: shmobile: defconfig: Disable CONFIG_EMBEDDED
arch/arm/configs/shmobile_defconfig | 6 +-----
drivers/tty/serial/Kconfig | 15 ++++++++++-----
2 files changed, 11 insertions(+), 10 deletions(-)
--
2.7.4
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2017-11-30 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 13:11 Geert Uytterhoeven [this message]
2017-11-30 13:11 ` [PATCH 1/5] tty: serial: sh-sci: Hide number of ports config question Geert Uytterhoeven
2017-11-30 13:11 ` [PATCH 2/5] tty: serial: sh-sci: Hide serial console " Geert Uytterhoeven
2017-11-30 13:12 ` [PATCH 3/5] tty: serial: sh-sci: Hide earlycon " Geert Uytterhoeven
2017-11-30 13:12 ` [PATCH 4/5] tty: serial: sh-sci: Hide DMA " Geert Uytterhoeven
2017-11-30 13:12 ` [PATCH/RFC 5/5] ARM: shmobile: defconfig: Disable CONFIG_EMBEDDED Geert Uytterhoeven
2017-12-01 8:33 ` Simon Horman
2017-12-04 9:46 ` Geert Uytterhoeven
2017-12-05 8:28 ` Simon Horman
2017-12-09 2:18 ` Rob Landley
2017-12-09 8:54 ` Geert Uytterhoeven
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=1512047522-16312-1-git-send-email-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=dalias@libc.org \
--cc=gregkh@linuxfoundation.org \
--cc=horms@verge.net.au \
--cc=jslaby@suse.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=ysato@users.sourceforge.jp \
/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).