From: sehro rautenkranz <sehro@sehro.org>
To: unlisted-recipients:; (no To-header on input)
Cc: sehro@sehro.org, Lidza Louina <lidza.louina@gmail.com>,
Mark Hounschell <markh@compro.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] staging: dgnc: Fix Kconfig help header and text
Date: Tue, 25 Sep 2018 09:53:09 -0600 [thread overview]
Message-ID: <20180925155309.15861-1-sehro@sehro.org> (raw)
In-Reply-To: <d5bb4ab0-42f6-3fd1-006d-670a355e8702@infradead.org>
Replace Kconfig help header and text to match other modules. Issue found
my checkpatch.
Spacing adjusted to match Documentation/process/coding-style.rst. Issue
reported by rdunlap@infradead.org.
Signed-off-by: sehro rautenkranz <sehro@sehro.org>
---
drivers/staging/dgnc/Kconfig | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/dgnc/Kconfig b/drivers/staging/dgnc/Kconfig
index c845b357b53d..7361d6cd73d4 100644
--- a/drivers/staging/dgnc/Kconfig
+++ b/drivers/staging/dgnc/Kconfig
@@ -3,8 +3,8 @@ config DGNC
default n
depends on TTY && PCI
help
- Say Y here to enable support for the Digi International Neo and
- Classic PCI based product line.
+ Say Y here to enable support for the Digi International Neo and
+ Classic PCI based product line.
- To compile this driver as a module, say M here: the module will be
- called dgnc
+ To compile this driver as a module, say M here: the module will be
+ called dgnc
--
2.19.0
next prev parent reply other threads:[~2018-09-25 15:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 6:20 [PATCH] staging: dgnc: Fix Kconfig help header and text sehro rautenkranz
2018-09-25 15:34 ` Randy Dunlap
2018-09-25 15:53 ` sehro rautenkranz [this message]
2018-09-25 16:00 ` Randy Dunlap
2018-09-25 16:22 ` sehro rautenkranz
2018-09-25 18:46 ` Greg Kroah-Hartman
2018-09-25 19:49 ` Randy Dunlap
2018-09-25 23:41 ` [PATCH v3] " Sehro Rautenkranz
[not found] ` <CA+t4uCMAgpNtpdLfxNY_cmx7WONKOYjiaTBDGRNd+7H_GUdRAA@mail.gmail.com>
2018-10-01 12:09 ` Mark Hounschell
[not found] ` <CA+t4uCPFZSTjyN-Wd3ppOp-edAXfSSTTdT8uab+-E53=Htv9+A@mail.gmail.com>
2018-10-01 17:38 ` Mark Hounschell
2018-10-02 22:09 ` Greg Kroah-Hartman
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=20180925155309.15861-1-sehro@sehro.org \
--to=sehro@sehro.org \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=lidza.louina@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/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).