From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-serial@vger.kernel.org
Subject: [PATCH 4/4 v2] serial: SH_SCI: improve "DMA support" prompt
Date: Sat, 10 Jan 2026 15:26:43 -0800 [thread overview]
Message-ID: <20260110232643.3533351-5-rdunlap@infradead.org> (raw)
In-Reply-To: <20260110232643.3533351-1-rdunlap@infradead.org>
Having a prompt of "DMA support" suddenly appear during a
"make oldconfig" can be confusing. Add a little helpful text to
the prompt message.
Fixes: 73a19e4c0301 ("serial: sh-sci: Add DMA support.")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
v2: make the prompt more like the other SH_SCI prompts (Geert)
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-serial@vger.kernel.org
drivers/tty/serial/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20260109.orig/drivers/tty/serial/Kconfig
+++ linux-next-20260109/drivers/tty/serial/Kconfig
@@ -671,7 +671,7 @@ config SERIAL_SH_SCI_EARLYCON
default ARCH_RENESAS
config SERIAL_SH_SCI_DMA
- bool "DMA support" if EXPERT
+ bool "Support for DMA on SuperH SCI(F)" if EXPERT
depends on SERIAL_SH_SCI && DMA_ENGINE
default ARCH_RENESAS
next prev parent reply other threads:[~2026-01-10 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 23:26 [PATCH 0/4 v2] serial: Kconfig cleanups Randy Dunlap
2026-01-10 23:26 ` [PATCH 1/4 v2] serial: imx: change SERIAL_IMX_CONSOLE to bool Randy Dunlap
2026-01-10 23:26 ` [PATCH 2/4 v2] serial: 8250: fix ordering of entries for menu display Randy Dunlap
2026-01-10 23:26 ` [PATCH 3/4 v2] serial: Kconfig: " Randy Dunlap
2026-01-10 23:26 ` Randy Dunlap [this message]
2026-01-12 10:03 ` [PATCH 4/4 v2] serial: SH_SCI: improve "DMA support" prompt 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=20260110232643.3533351-5-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.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