From: Robert Schwebel <r.schwebel@pengutronix.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: Robert Schwebel <r.schwebel@pengutronix.de>,
Jonathan Corbet <corbet@lwn.net>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [PATCH v2 1/5] docs: networking: nfc: change headlines to sphinx syntax
Date: Fri, 22 Nov 2019 08:43:02 +0100 [thread overview]
Message-ID: <20191122074306.78179-2-r.schwebel@pengutronix.de> (raw)
In-Reply-To: <20191122074306.78179-1-r.schwebel@pengutronix.de>
The headlines in this file do are not in the standard kernel docu-
mentation headline format. Change it, so this file can be switched to
rst in the future.
Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
---
Documentation/networking/nfc.txt | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/Documentation/networking/nfc.txt b/Documentation/networking/nfc.txt
index b24c29bdae27..c053610bfadc 100644
--- a/Documentation/networking/nfc.txt
+++ b/Documentation/networking/nfc.txt
@@ -1,3 +1,4 @@
+===================
Linux NFC subsystem
===================
@@ -8,7 +9,7 @@ This document covers the architecture overview, the device driver interface
description and the userspace interface description.
Architecture overview
----------------------
+=====================
The NFC subsystem is responsible for:
- NFC adapters management;
@@ -51,7 +52,7 @@ PF_NFC. The NFC_SOCKPROTO_RAW performs raw communication with NFC targets.
+-----------+
Device Driver Interface
------------------------
+=======================
When registering on the NFC subsystem, the device driver must inform the core
of the set of supported NFC protocols and the set of ops callbacks. The ops
@@ -64,7 +65,7 @@ callbacks that must be implemented are the following:
* data_exchange - send data and receive the response (transceive operation)
Userspace interface
---------------------
+===================
The userspace interface is divided in control operations and low-level data
exchange operation.
--
2.24.0
next prev parent reply other threads:[~2019-11-22 7:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 7:43 [PATCH v2 0/5] docs: networking: nfc: convert from txt to rst Robert Schwebel
2019-11-22 7:43 ` Robert Schwebel [this message]
2019-11-22 7:43 ` [PATCH v2 2/5] docs: networking: nfc: change block diagram to sphinx syntax Robert Schwebel
2019-11-22 7:43 ` [PATCH v2 3/5] docs: networking: nfc: fix bullet list syntax Robert Schwebel
2019-11-22 7:43 ` [PATCH v2 4/5] docs: networking: nfc: fix code block syntax Robert Schwebel
2019-11-22 7:43 ` [PATCH v2 5/5] docs: networking: nfc: change to rst format Robert Schwebel
2019-11-23 19:14 ` [PATCH v2 0/5] docs: networking: nfc: convert from txt to rst 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=20191122074306.78179-2-r.schwebel@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=linux-doc@vger.kernel.org \
--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).