From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: linux-gpio@vger.kernel.org
Cc: "Michael Buesch" <m@bues.ch>, "Jonathan Corbet" <corbet@lwn.net>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Bartosz Golaszewski" <bgolaszewski@baylibre.com>,
"Logan Gunthorpe" <logang@deltatee.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Mauro Carvalho Chehab" <mchehab+samsung@kernel.org>,
"Cornelia Huck" <cohuck@redhat.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] docs: driver-api: Move bt8xxgpio to the gpio directory
Date: Fri, 4 Oct 2019 18:40:55 +0200 [thread overview]
Message-ID: <20191004164059.10397-1-j.neuschaefer@gmx.net> (raw)
Let's declutter Documentation/driver-api a bit.
Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
---
Is this where we want to put documentation about specific GPIO
drivers/chips? Or perhaps under a subheading?
---
Documentation/driver-api/{ => gpio}/bt8xxgpio.rst | 0
Documentation/driver-api/gpio/index.rst | 1 +
Documentation/driver-api/index.rst | 1 -
drivers/gpio/Kconfig | 2 +-
4 files changed, 2 insertions(+), 2 deletions(-)
rename Documentation/driver-api/{ => gpio}/bt8xxgpio.rst (100%)
diff --git a/Documentation/driver-api/bt8xxgpio.rst b/Documentation/driver-api/gpio/bt8xxgpio.rst
similarity index 100%
rename from Documentation/driver-api/bt8xxgpio.rst
rename to Documentation/driver-api/gpio/bt8xxgpio.rst
diff --git a/Documentation/driver-api/gpio/index.rst b/Documentation/driver-api/gpio/index.rst
index c5b8467f9104..5b61032aa4ea 100644
--- a/Documentation/driver-api/gpio/index.rst
+++ b/Documentation/driver-api/gpio/index.rst
@@ -13,6 +13,7 @@ Contents:
board
drivers-on-gpio
legacy
+ bt8xxgpio
Core
====
diff --git a/Documentation/driver-api/index.rst b/Documentation/driver-api/index.rst
index 38e638abe3eb..2b3b6949381e 100644
--- a/Documentation/driver-api/index.rst
+++ b/Documentation/driver-api/index.rst
@@ -69,7 +69,6 @@ available subsections can be seen below.
fpga/index
acpi/index
backlight/lp855x-driver.rst
- bt8xxgpio
connector
console
dcdbas
diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
index 38e096e6925f..d96fb9923d30 100644
--- a/drivers/gpio/Kconfig
+++ b/drivers/gpio/Kconfig
@@ -1320,7 +1320,7 @@ config GPIO_BT8XX
The card needs to be physically altered for using it as a
GPIO card. For more information on how to build a GPIO card
from a BT8xx TV card, see the documentation file at
- Documentation/driver-api/bt8xxgpio.rst
+ Documentation/driver-api/gpio/bt8xxgpio.rst
If unsure, say N.
--
2.20.1
next reply other threads:[~2019-10-04 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 16:40 Jonathan Neuschäfer [this message]
2019-10-04 16:40 ` [PATCH 2/2] docs: driver-api: bt8xxgpio: Revive dead link Jonathan Neuschäfer
2019-10-04 17:14 ` Michael Büsch
2019-10-04 19:05 ` Mauro Carvalho Chehab
2019-10-09 9:14 ` Linus Walleij
2019-10-09 9:12 ` [PATCH 1/2] docs: driver-api: Move bt8xxgpio to the gpio directory Linus Walleij
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=20191004164059.10397-1-j.neuschaefer@gmx.net \
--to=j.neuschaefer@gmx.net \
--cc=bgolaszewski@baylibre.com \
--cc=cohuck@redhat.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=m@bues.ch \
--cc=mchehab+samsung@kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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).