netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rd.dunlab@gmail.com
To: netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>
Cc: rdunlap@infradead.org
Subject: [PATCH 2/3] Isolate CAIF transport drivers into their own menu
Date: Tue, 01 Oct 2019 16:04:00 -0700	[thread overview]
Message-ID: <20190920230359.122042646@gmail.com> (raw)
In-Reply-To: 20190920230358.973169240@gmail.com

[-- Attachment #1: drv-net-caif-menu.patch --]
[-- Type: text/plain, Size: 892 bytes --]

Isolate CAIF transport drivers into their own menu.

This cleans up the main Network device support menu,
makes it easier to find the CAIF drivers, and makes it
easier to enable/disable them as a group.

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Randy Dunlap <rdunlap@infradead.org>
---
 drivers/net/caif/Kconfig |   10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

--- lnx-53-caif.orig/drivers/net/caif/Kconfig
+++ lnx-53-caif/drivers/net/caif/Kconfig
@@ -3,7 +3,13 @@
 # CAIF physical drivers
 #
 
-comment "CAIF transport drivers"
+menuconfig CAIF_DRIVERS
+	bool "CAIF transport drivers"
+	depends on CAIF
+	help
+	  Enable this to see CAIF physical drivers.
+
+if CAIF_DRIVERS
 
 config CAIF_TTY
 	tristate "CAIF TTY transport driver"
@@ -55,3 +61,5 @@ config CAIF_VIRTIO
 if CAIF_VIRTIO
 source "drivers/vhost/Kconfig.vringh"
 endif
+
+endif # CAIF_DRIVERS



  parent reply	other threads:[~2019-10-02  3:44 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 ` [PATCH 1/3] Clean up the net/caif/Kconfig menu rd.dunlab
2019-10-01 23:04 ` rd.dunlab [this message]
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.122042646@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 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).