From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QXNiasO4cm4gU2xvdGggVMO4bm5lc2VuIDxhc3RAZmliZXJieS5uZXQ+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: donald.hunter@gmail.com, kuba@kernel.org, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
fmaurer@redhat.com, danieller@nvidia.com, fmancera@suse.de,
g.goller@proxmox.com, prohr@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/3] netlink: specs: rt-link: ipv6 devconf updates
Date: Tue, 01 Sep 2026 13:30:12 +0000 [thread overview]
Message-ID: <178826941214.1182020.17205509719306465886.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260831093458.472180-1-ast@fiberby.net>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 31 Aug 2026 09:34:52 +0000 you wrote:
> This series updates the doc-string for ifla-inet6-conf, and adds
> two missing ipv6-devconf enum values as identified by Sashiko
> during review of v1.
>
> Changes:
> v2:
> - Update commit message for net-next, and renamed from
> "netlink: specs: rt-link: fix ipv6 devconf doc"
> - Add Reviewed-by from Fernando (Thanks).
> - Sashiko comments:
> - Added missing enum members accept-ra-min-lft and force-forwarding
> as patch #2 and #3.
> - Re: data types: as Jakub wrote in the original commit 720447bd0b24
> ("netlink: specs: rt-link: remove implicit structs from devconf"):
> "u32 is probably best we can do right now", as the reality is that
> the sub-type varies per value.
> v1: https://lore.kernel.org/20260824103816.40040-1-ast@fiberby.net
>
> [...]
Here is the summary with links:
- [net-next,v2,1/3] netlink: specs: rt-link: update ipv6 devconf doc
https://git.kernel.org/netdev/net-next/c/5e63ade19044
- [net-next,v2,2/3] netlink: specs: rt-link: add accept-ra-min-lft
https://git.kernel.org/netdev/net-next/c/2b0aecb7b2b1
- [net-next,v2,3/3] netlink: specs: rt-link: add force-forwarding
https://git.kernel.org/netdev/net-next/c/f952040d7016
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-01 13:31 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 ` [PATCH net-next v2 2/3] netlink: specs: rt-link: add accept-ra-min-lft Asbjørn Sloth Tønnesen
2026-08-31 9:52 ` 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 ` patchwork-bot+netdevbpf [this message]
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=178826941214.1182020.17205509719306465886.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?QXNiasO4cm4gU2xvdGggVMO4bm5lc2VuIDxhc3RAZmliZXJieS5uZXQ+?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--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.