All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>
To: Donald Hunter <donald.hunter@gmail.com>,
	Jakub Kicinski <kuba@kernel.org>
Cc: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>,
	"David S . Miller" <davem@davemloft.net>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Simon Horman" <horms@kernel.org>,
	"Felix Maurer" <fmaurer@redhat.com>,
	"Danielle Ratson" <danieller@nvidia.com>,
	"Fernando Fernandez Mancera" <fmancera@suse.de>,
	"Gabriel Goller" <g.goller@proxmox.com>,
	"Patrick Rohr" <prohr@google.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next v2 2/3] netlink: specs: rt-link: add accept-ra-min-lft
Date: Mon, 31 Aug 2026 09:34:54 +0000	[thread overview]
Message-ID: <20260831093458.472180-3-ast@fiberby.net> (raw)
In-Reply-To: <20260831093458.472180-1-ast@fiberby.net>

Add missing enum member accept-ra-min-lft to ipv6-devconf.

In commit 1671bcfd76fd ("net: add sysctl accept_ra_min_rtr_lft")
the DEVCONF_* enum was extended with DEVCONF_ACCEPT_RA_MIN_RTR_LFT.

It was renamed to DEVCONF_ACCEPT_RA_MIN_LFT in commit 5027d54a9c30
("net: change accept_ra_min_rtr_lft to affect all RA lifetimes").

Shortly thereafter, this spec was introduced in commit b2f63d904e72
("doc/netlink: Add spec for rt link messages").

This pre-existing issue was detected by Sashiko, when reviewing the
first patch in this series.

Link: https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260824103816.40040-1-ast%40fiberby.net
Signed-off-by: Asbjørn Sloth Tønnesen <ast@fiberby.net>
---
 Documentation/netlink/specs/rt-link.yaml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Documentation/netlink/specs/rt-link.yaml b/Documentation/netlink/specs/rt-link.yaml
index 00c915031efd..ab677801cde8 100644
--- a/Documentation/netlink/specs/rt-link.yaml
+++ b/Documentation/netlink/specs/rt-link.yaml
@@ -494,6 +494,8 @@ definitions:
         name: ndisc-evict-nocarrier
       -
         name: accept-untracked-na
+      -
+        name: accept-ra-min-lft
   -
     name: ifla-icmp6-stats
     enum-name:
-- 
2.55.0


  parent reply	other threads:[~2026-08-31  9:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  9:34 [PATCH net-next v2 0/3] netlink: specs: rt-link: ipv6 devconf updates Asbjørn Sloth Tønnesen
2026-08-31  9:34 ` [PATCH net-next v2 1/3] netlink: specs: rt-link: update ipv6 devconf doc Asbjørn Sloth Tønnesen
2026-08-31  9:34 ` Asbjørn Sloth Tønnesen [this message]
2026-08-31  9:52   ` [PATCH net-next v2 2/3] netlink: specs: rt-link: add accept-ra-min-lft Fernando Fernandez Mancera
2026-08-31  9:34 ` [PATCH net-next v2 3/3] netlink: specs: rt-link: add force-forwarding Asbjørn Sloth Tønnesen
2026-08-31  9:53   ` Fernando Fernandez Mancera
2026-08-31 12:54   ` Gabriel Goller
2026-09-01 13:30 ` [PATCH net-next v2 0/3] netlink: specs: rt-link: ipv6 devconf updates patchwork-bot+netdevbpf

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=20260831093458.472180-3-ast@fiberby.net \
    --to=ast@fiberby.net \
    --cc=danieller@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=fmancera@suse.de \
    --cc=fmaurer@redhat.com \
    --cc=g.goller@proxmox.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=prohr@google.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 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.