From: Randy Dunlap <rdunlap@infradead.org>
To: Simon Que <sque@chromium.org>, linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ben Chan <benchan@chromium.org>,
Chun-Ta Lin <itspeter@chromium.org>,
Zhongze Hu <frankhu@chromium.org>, Joe Perches <joe@perches.com>,
Rob Springer <rspringer@google.com>,
John Joseph <jnjoseph@google.com>
Subject: Re: [PATCH v6] drivers/staging: Gasket driver framework + Apex driver
Date: Fri, 29 Jun 2018 17:17:47 -0700 [thread overview]
Message-ID: <d46ff130-45b5-d971-94f2-1650de891682@infradead.org> (raw)
In-Reply-To: <20180630000253.70103-1-sque@chromium.org>
On 06/29/18 17:02, Simon Que wrote:
> diff --git a/drivers/staging/gasket/Kconfig b/drivers/staging/gasket/Kconfig
> new file mode 100644
> index 000000000000..3465e8510fc2
> --- /dev/null
> +++ b/drivers/staging/gasket/Kconfig
> @@ -0,0 +1,23 @@
> +menu "Gasket devices"
> +
> +config STAGING_GASKET_FRAMEWORK
> + tristate "Gasket framework"
> + depends on PCI
> + help
> + This framework supports Gasket-compatible devices, such as Apex.
> + It is required for either of those modules.
Either of what modules?
Maybe "for any of those modules." ?
Also, Kconfig help text indentation is (from Documentation/process/coding-style.rst):
Lines under a ``config`` definition are indented with one tab, while help text
is indented an additional two spaces.
so one tab + 2 spaces, please, above and below here.
> +
> + To compile this driver as a module, choose M here. The module
> + will be called "gasket".
> +
> +config STAGING_APEX_DRIVER
> + tristate "Apex Driver"
> + depends on STAGING_GASKET_FRAMEWORK
> + help
> + This driver supports the Apex device. Say Y if you want to
> + include this driver in the kernel.
> +
> + To compile this driver as a module, choose M here. The module
> + will be called "apex".
> +
> +endmenu
--
~Randy
next prev parent reply other threads:[~2018-06-30 0:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 0:02 Simon Que
2018-06-30 0:17 ` Randy Dunlap [this message]
2018-06-30 5:32 ` kbuild test robot
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=d46ff130-45b5-d971-94f2-1650de891682@infradead.org \
--to=rdunlap@infradead.org \
--cc=benchan@chromium.org \
--cc=frankhu@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=itspeter@chromium.org \
--cc=jnjoseph@google.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rspringer@google.com \
--cc=sque@chromium.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
all inboxes | Powered by JetHome®