From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH 6/8] docs: video-output.txt: convert it to ReST format
Date: Wed, 10 Apr 2019 06:56:25 -0300 [thread overview]
Message-ID: <0a11af54345d0d8bc4e0664ab5b27ef0dddd267e.1554889999.git.mchehab+samsung@kernel.org> (raw)
In-Reply-To: <cover.1554889999.git.mchehab+samsung@kernel.org>
This file doesn't follow the documentation style we use
within the Kernel. Fix it.
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
---
Documentation/video-output.txt | 52 +++++++++++++++++-----------------
1 file changed, 26 insertions(+), 26 deletions(-)
diff --git a/Documentation/video-output.txt b/Documentation/video-output.txt
index e517011be4f9..56d6fa2e2368 100644
--- a/Documentation/video-output.txt
+++ b/Documentation/video-output.txt
@@ -1,34 +1,34 @@
+Video Output Switcher Control
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Video Output Switcher Control
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- 2006 luming.yu@intel.com
+2006 luming.yu@intel.com
The output sysfs class driver provides an abstract video output layer that
can be used to hook platform specific methods to enable/disable video output
device through common sysfs interface. For example, on my IBM ThinkPad T42
laptop, The ACPI video driver registered its output devices and read/write
-method for 'state' with output sysfs class. The user interface under sysfs is:
+method for 'state' with output sysfs class. The user interface under sysfs is::
-linux:/sys/class/video_output # tree .
-.
-|-- CRT0
-| |-- device -> ../../../devices/pci0000:00/0000:00:01.0
-| |-- state
-| |-- subsystem -> ../../../class/video_output
-| `-- uevent
-|-- DVI0
-| |-- device -> ../../../devices/pci0000:00/0000:00:01.0
-| |-- state
-| |-- subsystem -> ../../../class/video_output
-| `-- uevent
-|-- LCD0
-| |-- device -> ../../../devices/pci0000:00/0000:00:01.0
-| |-- state
-| |-- subsystem -> ../../../class/video_output
-| `-- uevent
-`-- TV0
- |-- device -> ../../../devices/pci0000:00/0000:00:01.0
- |-- state
- |-- subsystem -> ../../../class/video_output
- `-- uevent
+ linux:/sys/class/video_output # tree .
+ .
+ |-- CRT0
+ | |-- device -> ../../../devices/pci0000:00/0000:00:01.0
+ | |-- state
+ | |-- subsystem -> ../../../class/video_output
+ | `-- uevent
+ |-- DVI0
+ | |-- device -> ../../../devices/pci0000:00/0000:00:01.0
+ | |-- state
+ | |-- subsystem -> ../../../class/video_output
+ | `-- uevent
+ |-- LCD0
+ | |-- device -> ../../../devices/pci0000:00/0000:00:01.0
+ | |-- state
+ | |-- subsystem -> ../../../class/video_output
+ | `-- uevent
+ `-- TV0
+ |-- device -> ../../../devices/pci0000:00/0000:00:01.0
+ |-- state
+ |-- subsystem -> ../../../class/video_output
+ `-- uevent
--
2.20.1
next prev parent reply other threads:[~2019-04-10 9:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 9:56 [PATCH 0/8] Prepare files under Documentation/*.txt to build with Sphinx Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 1/8] docs: DMA-API-HOWTO: add a missing "=" Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 2/8] docs: atomic_bitops.txt: add a title for this document Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 3/8] docs: clearing-warn-once.txt: " Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 4/8] docs: ntb.txt: use Sphinx notation for the two ascii figures Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 5/8] docs: unaligned-memory-access.txt: use a lowercase title Mauro Carvalho Chehab
2019-04-10 9:56 ` Mauro Carvalho Chehab [this message]
2019-04-10 9:56 ` [PATCH 7/8] docs: ntb.txt: add blank lines to clean up some Sphinx warnings Mauro Carvalho Chehab
2019-04-10 9:56 ` [PATCH 8/8] docs: speculation.txt: mark example blocks as such Mauro Carvalho Chehab
2019-04-11 18:37 ` [PATCH 0/8] Prepare files under Documentation/*.txt to build with Sphinx Jonathan Corbet
2019-04-12 10:21 ` David Howells
2019-04-12 10:31 ` Markus Heiser
2019-04-12 12:19 ` David Howells
2019-04-12 12:34 ` Markus Heiser
2019-04-12 15:39 ` Jonathan Corbet
2019-04-12 16:45 ` Markus Heiser
2019-04-12 14:13 ` Jani Nikula
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=0a11af54345d0d8bc4e0664ab5b27ef0dddd267e.1554889999.git.mchehab+samsung@kernel.org \
--to=mchehab+samsung@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.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®