netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
	Jakub Kicinski <kuba@kernel.org>,
	t.sailer@alumni.ethz.ch
Subject: [RFC 3/8] docs: networking: move baycom to the hw driver section
Date: Thu, 11 Jun 2020 10:30:05 -0700	[thread overview]
Message-ID: <20200611173010.474475-4-kuba@kernel.org> (raw)
In-Reply-To: <20200611173010.474475-1-kuba@kernel.org>

Move baycom to hamradio.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>
--
CC: t.sailer@alumni.ethz.ch
---
 .../networking/{ => device_drivers/hamradio}/baycom.rst   | 0
 .../networking/device_drivers/hamradio/index.rst          | 1 +
 Documentation/networking/index.rst                        | 1 -
 drivers/net/hamradio/Kconfig                              | 8 ++++----
 4 files changed, 5 insertions(+), 5 deletions(-)
 rename Documentation/networking/{ => device_drivers/hamradio}/baycom.rst (100%)

diff --git a/Documentation/networking/baycom.rst b/Documentation/networking/device_drivers/hamradio/baycom.rst
similarity index 100%
rename from Documentation/networking/baycom.rst
rename to Documentation/networking/device_drivers/hamradio/baycom.rst
diff --git a/Documentation/networking/device_drivers/hamradio/index.rst b/Documentation/networking/device_drivers/hamradio/index.rst
index df03a5acbfa7..7e731732057b 100644
--- a/Documentation/networking/device_drivers/hamradio/index.rst
+++ b/Documentation/networking/device_drivers/hamradio/index.rst
@@ -8,6 +8,7 @@ Amateur Radio Device Drivers
 .. toctree::
    :maxdepth: 2
 
+   baycom
    z8530drv
 
 .. only::  subproject and html
diff --git a/Documentation/networking/index.rst b/Documentation/networking/index.rst
index 718e04e3f7ed..76831e9d7c9a 100644
--- a/Documentation/networking/index.rst
+++ b/Documentation/networking/index.rst
@@ -43,7 +43,6 @@ Linux Networking Documentation
    arcnet
    atm
    ax25
-   baycom
    bonding
    cdc_mbim
    cops
diff --git a/drivers/net/hamradio/Kconfig b/drivers/net/hamradio/Kconfig
index 6aaca62940d0..8e63afc8a2e6 100644
--- a/drivers/net/hamradio/Kconfig
+++ b/drivers/net/hamradio/Kconfig
@@ -129,7 +129,7 @@ config BAYCOM_SER_FDX
 	  your serial interface chip. To configure the driver, use the sethdlc
 	  utility available in the standard ax25 utilities package. For
 	  information on the modems, see <http://www.baycom.de/> and
-	  <file:Documentation/networking/baycom.rst>.
+	  <file:Documentation/networking/device_drivers/hamradio/baycom.rst>.
 
 	  To compile this driver as a module, choose M here: the module
 	  will be called baycom_ser_fdx.  This is recommended.
@@ -147,7 +147,7 @@ config BAYCOM_SER_HDX
 	  the driver, use the sethdlc utility available in the standard ax25
 	  utilities package. For information on the modems, see
 	  <http://www.baycom.de/> and
-	  <file:Documentation/networking/baycom.rst>.
+	  <file:Documentation/networking/device_drivers/hamradio/baycom.rst>.
 
 	  To compile this driver as a module, choose M here: the module
 	  will be called baycom_ser_hdx.  This is recommended.
@@ -162,7 +162,7 @@ config BAYCOM_PAR
 	  par96 designs. To configure the driver, use the sethdlc utility
 	  available in the standard ax25 utilities package. For information on
 	  the modems, see <http://www.baycom.de/> and the file
-	  <file:Documentation/networking/baycom.rst>.
+	  <file:Documentation/networking/device_drivers/hamradio/baycom.rst>.
 
 	  To compile this driver as a module, choose M here: the module
 	  will be called baycom_par.  This is recommended.
@@ -177,7 +177,7 @@ config BAYCOM_EPP
 	  designs. To configure the driver, use the sethdlc utility available
 	  in the standard ax25 utilities package. For information on the
 	  modems, see <http://www.baycom.de/> and the file
-	  <file:Documentation/networking/baycom.rst>.
+	  <file:Documentation/networking/device_drivers/hamradio/baycom.rst>.
 
 	  To compile this driver as a module, choose M here: the module
 	  will be called baycom_epp.  This is recommended.
-- 
2.26.2


  parent reply	other threads:[~2020-06-11 17:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 17:30 [RFC 0/8] net: organize driver docs by device type Jakub Kicinski
2020-06-11 17:30 ` [RFC 1/8] docs: networking: reorganize driver documentation again Jakub Kicinski
2020-06-11 21:17   ` Kirsher, Jeffrey T
2020-06-11 21:49     ` Jakub Kicinski
2020-06-11 22:18     ` Stephen Hemminger
2020-06-11 23:09       ` Jakub Kicinski
2020-06-11 23:43         ` Kirsher, Jeffrey T
2020-06-12 23:56   ` Shannon Nelson
2020-06-11 17:30 ` [RFC 2/8] docs: networking: move z8530 to the hw driver section Jakub Kicinski
2020-06-11 17:30 ` Jakub Kicinski [this message]
2020-06-11 17:30 ` [RFC 4/8] docs: networking: move ray_cs " Jakub Kicinski
2020-06-11 17:30 ` [RFC 5/8] docs: networking: move remaining Ethernet driver docs to the hw section Jakub Kicinski
2020-06-11 17:30 ` [RFC 6/8] docs: networking: move AppleTalk / LocalTalk drivers to the hw driver section Jakub Kicinski
2020-06-11 17:30 ` [RFC 7/8] docs: networking: move ATM " Jakub Kicinski
2020-06-11 17:30 ` [RFC 8/8] docs: networking: move FDDI " Jakub Kicinski

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=20200611173010.474475-4-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=t.sailer@alumni.ethz.ch \
    /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).