From: rd.dunlab@gmail.com
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>
Cc: rdunlap@infradead.org
Subject: [PATCH 1/3] Clean up the net/caif/Kconfig menu
Date: Tue, 01 Oct 2019 16:03:59 -0700 [thread overview]
Message-ID: <20190920230359.064400931@gmail.com> (raw)
In-Reply-To: 20190920230358.973169240@gmail.com
[-- Attachment #1: net-caif-Kconfig-clean001.patch --]
[-- Type: text/plain, Size: 1723 bytes --]
Clean up the net/caif/Kconfig menu:
- remove extraneous space
- minor language tweaks
- fix punctuation
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Randy Dunlap <rdunlap@infradead.org>
---
net/caif/Kconfig | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
--- lnx-53-caif.orig/net/caif/Kconfig
+++ lnx-53-caif/net/caif/Kconfig
@@ -13,11 +13,11 @@ menuconfig CAIF
with its modems. It is accessed from user space as sockets (PF_CAIF).
Say Y (or M) here if you build for a phone product (e.g. Android or
- MeeGo ) that uses CAIF as transport, if unsure say N.
+ MeeGo) that uses CAIF as transport. If unsure say N.
If you select to build it as module then CAIF_NETDEV also needs to be
- built as modules. You will also need to say yes to any CAIF physical
- devices that your platform requires.
+ built as a module. You will also need to say Y (or M) to any CAIF
+ physical devices that your platform requires.
See Documentation/networking/caif for a further explanation on how to
use and configure CAIF.
@@ -37,7 +37,7 @@ config CAIF_NETDEV
default CAIF
---help---
Say Y if you will be using a CAIF based GPRS network device.
- This can be either built-in or a loadable module,
+ This can be either built-in or a loadable module.
If you select to build it as a built-in then the main CAIF device must
also be a built-in.
If unsure say Y.
@@ -48,7 +48,7 @@ config CAIF_USB
default n
---help---
Say Y if you are using CAIF over USB CDC NCM.
- This can be either built-in or a loadable module,
+ This can be either built-in or a loadable module.
If you select to build it as a built-in then the main CAIF device must
also be a built-in.
If unsure say N.
next prev parent reply other threads:[~2019-10-02 3:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 23:03 [PATCH 0/3] CAIF Kconfig fixes rd.dunlab
2019-10-01 23:03 ` rd.dunlab [this message]
2019-10-01 23:04 ` [PATCH 2/3] Isolate CAIF transport drivers into their own menu rd.dunlab
2019-10-01 23:04 ` [PATCH 3/3] Minor fixes to the CAIF Transport drivers Kconfig file rd.dunlab
2019-10-02 21:48 ` [PATCH 0/3] CAIF Kconfig fixes David Miller
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=20190920230359.064400931@gmail.com \
--to=rd.dunlab@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@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 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.