From: Masatake YAMATO <yamato@redhat.com>
To: netdev@vger.kernel.org
Cc: yamato@redhat.com
Subject: [PATCH iproute2 1/2] man: explain the naming convention of files under .d dir
Date: Thu, 18 Dec 2025 00:43:53 +0900 [thread overview]
Message-ID: <20251217154354.2410098-1-yamato@redhat.com> (raw)
Signed-off-by: Masatake YAMATO <yamato@redhat.com>
---
man/man8/ip-address.8.in | 7 +++++++
man/man8/ip-link.8.in | 7 +++++--
2 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/man/man8/ip-address.8.in b/man/man8/ip-address.8.in
index 79942c1a..e88a114f 100644
--- a/man/man8/ip-address.8.in
+++ b/man/man8/ip-address.8.in
@@ -331,6 +331,13 @@ values have a fixed interpretation. Namely:
The rest of the values are not reserved and the administrator is free
to assign (or not to assign) protocol tags.
+When scanning
+.BR rt_addrprotos.d
+directory, only files ending
+.BR .conf
+are considered.
+Files beginning with a dot are ignored.
+
.SS ip address delete - delete protocol address
.B Arguments:
coincide with the arguments of
diff --git a/man/man8/ip-link.8.in b/man/man8/ip-link.8.in
index ef45fe08..67f9e2f0 100644
--- a/man/man8/ip-link.8.in
+++ b/man/man8/ip-link.8.in
@@ -2315,8 +2315,11 @@ down on the switch port.
.BR "protodown_reason PREASON on " or " off"
set
.B PROTODOWN
-reasons on the device. protodown reason bit names can be enumerated under
-/etc/iproute2/protodown_reasons.d/. possible reasons bits 0-31
+reasons on the device. protodown reason bit names can be enumerated in the
+.BR *.conf
+files under
+.BR @SYSCONF_USR_DIR@/protodown_reasons.d " or " @SYSCONF_ETC_DIR@/protodown_reasons.d "."
+possible reasons bits 0-31
.TP
.BR "dynamic on " or " dynamic off"
--
2.51.0
next reply other threads:[~2025-12-17 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 15:43 Masatake YAMATO [this message]
2025-12-22 18:32 ` [PATCH iproute2 1/2] man: explain the naming convention of files under .d dir Stephen Hemminger
2025-12-22 22:42 ` Masatake YAMATO
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=20251217154354.2410098-1-yamato@redhat.com \
--to=yamato@redhat.com \
--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).