From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Dorine Tipo <dorine.a.tipo@gmail.com>,
Linux Outreachy <outreachy@lists.linux.dev>,
Greg KH <gregkh@linuxfoundation.org>,
Linux Staging Drivers <linux-staging@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Martyn Welch <martyn@welchs.me.uk>,
Manohar Vanga <manohar.vanga@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Charles Han <hanchunchao@inspur.com>
Subject: Re: [PATCH] staging: vme: enhance the help paragraphs for clarity
Date: Wed, 1 Nov 2023 14:39:53 +0700 [thread overview]
Message-ID: <ZUIAyQGSfIKqK7AE@debian.me> (raw)
In-Reply-To: <20231029180346.8570-1-dorine.a.tipo@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]
[Cc'ing driver contributors found via get_maintainer.pl. Also Cc: Charles from
linux-doc mailing list as wording patches like this one most likely suit him.]
On Sun, Oct 29, 2023 at 06:03:46PM +0000, Dorine Tipo wrote:
> diff --git a/drivers/staging/vme_user/Kconfig b/drivers/staging/vme_user/Kconfig
> index d65cc5510649..65a3e769090d 100644
> --- a/drivers/staging/vme_user/Kconfig
> +++ b/drivers/staging/vme_user/Kconfig
> @@ -4,6 +4,11 @@ menuconfig VME_BUS
> depends on PCI
> help
> If you say Y here you get support for the VME bridge Framework.
> + The VME Bridge Framework provides a set of tools and drivers
> + for VMEbus systems, allowing seamless integration of VME devices
> + with your PCI-enabled hardware. Select 'Y' to enable this feature
> + if you have VMEbus-based hardware or intend to use VME devices in
> + your system.
>
> if VME_BUS
>
> @@ -14,7 +19,10 @@ config VME_TSI148
> depends on HAS_DMA
> help
> If you say Y here you get support for the Tundra TSI148 VME bridge
> - chip.
> + chip. This bridge chip provides compatibility for VMEbus systems, allowing
> + communication with various VME devices. If you have hardware that
> + includes the Tundra TSI148 VME bridge, or if you plan to use VME
> + devices with your system, choose 'Y' to enable this feature.
Dorine,
Are you sure that your description properly describes what these modules
are doing? And most importantly, when users select them as module (choose
M), what will the modules be named?
Confused...
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-01 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 18:03 [PATCH] staging: vme: enhance the help paragraphs for clarity Dorine Tipo
2023-10-30 6:25 ` Julia Lawall
2023-11-01 7:39 ` Bagas Sanjaya [this message]
2023-11-01 8:09 ` Greg KH
2023-11-01 8:14 ` Bagas Sanjaya
2023-11-01 11:48 ` Dorine Tipo
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=ZUIAyQGSfIKqK7AE@debian.me \
--to=bagasdotme@gmail.com \
--cc=dorine.a.tipo@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hanchunchao@inspur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lukas.bulwahn@gmail.com \
--cc=manohar.vanga@gmail.com \
--cc=martyn@welchs.me.uk \
--cc=outreachy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.