public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: Baruch Siach <baruch@tkos.co.il>,
	linux-man@vger.kernel.org,
	Alejandro Colomar <alx.manpages@gmail.com>
Subject: [PATCH] packet.7: Update references to kernel documentation
Date: Tue, 15 Dec 2020 19:17:34 +0100	[thread overview]
Message-ID: <20201215181732.22155-1-alx.manpages@gmail.com> (raw)

From: Baruch Siach <baruch@tkos.co.il>

Files moved from .txt to .rst.

Also, drop / prefix from kernel source tree references.

Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
 man7/packet.7 | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/man7/packet.7 b/man7/packet.7
index ac1c60905..856c59e6b 100644
--- a/man7/packet.7
+++ b/man7/packet.7
@@ -405,7 +405,7 @@ equal to
 .IP
 Packet sockets implement multiple variants of the packet ring.
 The implementation details are described in
-.IR Documentation/networking/packet_mmap.txt
+.IR Documentation/networking/packet_mmap.rst
 in the Linux kernel source tree.
 .TP
 .BR PACKET_STATISTICS
@@ -431,7 +431,7 @@ By default, this is a software generated timestamp generated when the
 packet is copied into the ring.
 This integer option selects the type of timestamp.
 Besides the default, it support the two hardware formats described in
-.IR Documentation/networking/timestamping.txt
+.IR Documentation/networking/timestamping.rst
 in the Linux kernel source tree.
 .TP
 .BR PACKET_TX_RING " (since Linux 2.6.31)"
@@ -648,9 +648,9 @@ The
 include file for physical-layer protocols.
 .PP
 The Linux kernel source tree.
-.IR /Documentation/networking/filter.txt
+.IR Documentation/networking/filter.rst
 describes how to apply Berkeley Packet Filters to packet sockets.
-.IR /tools/testing/selftests/net/psock_tpacket.c
+.IR tools/testing/selftests/net/psock_tpacket.c
 contains example source code for all available versions of
 .BR PACKET_RX_RING
 and

base-commit: 27482d700b5d2d062f994bee2c79aac7a5d9d17c
-- 
2.29.2


             reply	other threads:[~2020-12-15 18:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-15 18:17 Alejandro Colomar [this message]
2020-12-18 10:39 ` Ping: [PATCH] packet.7: Update references to kernel documentation Alejandro Colomar (man-pages)
2020-12-20 14:49 ` Michael Kerrisk (man-pages)
  -- strict thread matches above, loose matches on Subject: below --
2020-12-15 17:54 Baruch Siach
2020-12-15 18:03 ` Alejandro Colomar (man-pages)

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=20201215181732.22155-1-alx.manpages@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=baruch@tkos.co.il \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.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