All of lore.kernel.org
 help / color / mirror / Atom feed
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 4/5] docs: networking: nfc: fix code block syntax
Date: Fri, 22 Nov 2019 08:43:05 +0100	[thread overview]
Message-ID: <20191122074306.78179-5-r.schwebel@pengutronix.de> (raw)
In-Reply-To: <20191122074306.78179-1-r.schwebel@pengutronix.de>

Silence this warning:

Documentation/networking/nfc.rst:113: WARNING: Definition list ends without
a blank line; unexpected unindent.

Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
---
 Documentation/networking/nfc.txt | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/Documentation/networking/nfc.txt b/Documentation/networking/nfc.txt
index af69b3a90eaa..9aab3a88c9b2 100644
--- a/Documentation/networking/nfc.txt
+++ b/Documentation/networking/nfc.txt
@@ -103,14 +103,14 @@ it's closed.
 LOW-LEVEL DATA EXCHANGE:
 
 The userspace must use PF_NFC sockets to perform any data communication with
-targets. All NFC sockets use AF_NFC:
-
-struct sockaddr_nfc {
-       sa_family_t sa_family;
-       __u32 dev_idx;
-       __u32 target_idx;
-       __u32 nfc_protocol;
-};
+targets. All NFC sockets use AF_NFC::
+
+        struct sockaddr_nfc {
+               sa_family_t sa_family;
+               __u32 dev_idx;
+               __u32 target_idx;
+               __u32 nfc_protocol;
+        };
 
 To establish a connection with one target, the user must create an
 NFC_SOCKPROTO_RAW socket and call the 'connect' syscall with the sockaddr_nfc
-- 
2.24.0


  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 ` [PATCH v2 1/5] docs: networking: nfc: change headlines to sphinx syntax Robert Schwebel
2019-11-22  7:43 ` [PATCH v2 2/5] docs: networking: nfc: change block diagram " 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 ` Robert Schwebel [this message]
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-5-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.