From: patchwork-bot+netdevbpf@kernel.org
To: Arun Ajith S <aajith@arista.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
dsahern@kernel.org, yoshfuji@linux-ipv6.org, kuba@kernel.org,
pabeni@redhat.com, corbet@lwn.net, prestwoj@gmail.com,
gilligan@arista.com, noureddine@arista.com, gk@arista.com
Subject: Re: [PATCH net-next v6] net/ipv6: Introduce accept_unsolicited_na knob to implement router-side changes for RFC9131
Date: Sun, 17 Apr 2022 12:30:10 +0000 [thread overview]
Message-ID: <165019861094.3969.10708842046305944701.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220415083402.39080-1-aajith@arista.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 15 Apr 2022 08:34:02 +0000 you wrote:
> Add a new neighbour cache entry in STALE state for routers on receiving
> an unsolicited (gratuitous) neighbour advertisement with
> target link-layer-address option specified.
> This is similar to the arp_accept configuration for IPv4.
> A new sysctl endpoint is created to turn on this behaviour:
> /proc/sys/net/ipv6/conf/interface/accept_unsolicited_na.
>
> [...]
Here is the summary with links:
- [net-next,v6] net/ipv6: Introduce accept_unsolicited_na knob to implement router-side changes for RFC9131
https://git.kernel.org/netdev/net-next/c/f9a2fb73318e
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:[~2022-04-17 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 8:34 Arun Ajith S
2022-04-16 5:43 ` Bagas Sanjaya
2022-04-16 12:20 ` Arun Ajith S
2022-04-17 12: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=165019861094.3969.10708842046305944701.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aajith@arista.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=gilligan@arista.com \
--cc=gk@arista.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noureddine@arista.com \
--cc=pabeni@redhat.com \
--cc=prestwoj@gmail.com \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®