From: Dan Carpenter <dan.carpenter@linaro.org>
To: Jacob Lott <jklott.git@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: rts5208: Add more details to Kconfig help
Date: Fri, 19 Jan 2024 09:34:36 +0300 [thread overview]
Message-ID: <ce1d6680-a7f5-4939-a47c-3079e7136c28@moroto.mountain> (raw)
In-Reply-To: <20240118191703.89535-1-jklott.git@gmail.com>
On Thu, Jan 18, 2024 at 02:17:04PM -0500, Jacob Lott wrote:
> The current help text is short and triggers a
> warning from checkpatch.pl. This patch adds more
> details to the help text which should provide better
> information for whether or not to enable the driver.
>
> Signed-off-by: Jacob Lott <jklott.git@gmail.com>
> ---
> v2 -> v3: Fixed spacing and newline in text
The commit message is still not line wrapped correctly at 72-75
characters. It should have been:
The current help text is short and triggers a warning from checkpatch.pl.
This patch adds more details to the help text which should provide better
information for whether or not to enable the driver.
Or:
The current help text is short and triggers a warning from
checkpatch.pl. This patch adds more details to the help text which
should provide better information for whether or not to enable the
driver.
> v1 -> v2: Corrected line spacing based off feedback
>
> drivers/staging/rts5208/Kconfig | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/rts5208/Kconfig b/drivers/staging/rts5208/Kconfig
> index b864023d3ccb..c4664a26ba3b 100644
> --- a/drivers/staging/rts5208/Kconfig
> +++ b/drivers/staging/rts5208/Kconfig
> @@ -3,7 +3,11 @@ config RTS5208
> tristate "Realtek PCI-E Card Reader RTS5208/5288 support"
> depends on PCI && SCSI
> help
> - Say Y here to include driver code to support the Realtek
> - PCI-E card reader rts5208/rts5288.
> + Choose Y here to enable support for the Realtek PCI-E card reader
> + RTS5208/5288. This driver facilitates communication between the Linux
> + kernel and the Realtek PCI-E card reader.
>
> - If this driver is compiled as a module, it will be named rts5208.
> + If you opt to compile this driver as a module, it will be named rts5208.
> + Selecting N will exclude this driver from the kernel build. Choose option
> + Y if your system includes the Realtek PCI-E card reader rts5208/rts5288.
> + When in doubt, it is generally safe to select N.
In the original code there were three lines of help text.
1) Say Y here to include driver code to support the Realtek
2) PCI-E card reader rts5208/rts5288.
3) If this driver is compiled as a module, it will be named rts5208.
The minimum that checkpatch wants is 4 lines.
However, I feel like nothing you're adding here is useful information.
Some of it is just confusing like, "This driver facilitates
communication between the Linux kernel and the Realtek PCI-E card
reader." That line feels like information, but when you think about it,
it doesn't actually mean anything. The second paragraph is just
repeated information so it's kind of a waste of time.
Don't just obey checkpatch for the sake of obeying, if we can't think
of anything else useful to say then three lines is enough.
regards,
dan carpenter
next prev parent reply other threads:[~2024-01-19 6:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 19:17 Jacob Lott
2024-01-19 6:34 ` Dan Carpenter [this message]
2024-01-19 11:42 ` Jacob Lott
2024-01-19 13:14 ` Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2024-01-18 19:14 Jacob Lott
2024-01-19 5:56 ` Greg KH
2024-01-18 17:59 Jacob Lott
2024-01-18 18:59 ` Greg KH
2024-01-18 19:19 ` Randy Dunlap
2024-01-18 19:21 ` Jacob Lott
2024-01-18 16:54 Jacob Lott
2024-01-18 17:53 ` Greg KH
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=ce1d6680-a7f5-4939-a47c-3079e7136c28@moroto.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jklott.git@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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
all inboxes | Powered by JetHome®