All of lore.kernel.org
 help / color / mirror / Atom feed
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,
	linux-kselftest@vger.kernel.org, dsahern@kernel.org,
	bagasdotme@gmail.com, yoshfuji@linux-ipv6.org, kuba@kernel.org,
	pabeni@redhat.com, prestwoj@gmail.com, corbet@lwn.net,
	justin.iurman@uliege.be, edumazet@google.com, shuah@kernel.org,
	gilligan@arista.com, noureddine@arista.com, gk@arista.com
Subject: Re: [PATCH net v3] net/ipv6: Expand and rename accept_unsolicited_na to accept_untracked_na
Date: Tue, 31 May 2022 10:30:12 +0000	[thread overview]
Message-ID: <165399301210.20049.4916718889396503878.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220530101414.65439-1-aajith@arista.com>

Hello:

This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:

On Mon, 30 May 2022 10:14:14 +0000 you wrote:
> RFC 9131 changes default behaviour of handling RX of NA messages when the
> corresponding entry is absent in the neighbour cache. The current
> implementation is limited to accept just unsolicited NAs. However, the
> RFC is more generic where it also accepts solicited NAs. Both types
> should result in adding a STALE entry for this case.
> 
> Expand accept_untracked_na behaviour to also accept solicited NAs to
> be compliant with the RFC and rename the sysctl knob to
> accept_untracked_na.
> 
> [...]

Here is the summary with links:
  - [net,v3] net/ipv6: Expand and rename accept_unsolicited_na to accept_untracked_na
    https://git.kernel.org/netdev/net/c/3e0b8f529c10

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-05-31 10:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-30 10:14 [PATCH net v3] net/ipv6: Expand and rename accept_unsolicited_na to accept_untracked_na Arun Ajith S
2022-05-30 16:22 ` David Ahern
2022-05-31 10: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=165399301210.20049.4916718889396503878.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aajith@arista.com \
    --cc=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=gilligan@arista.com \
    --cc=gk@arista.com \
    --cc=justin.iurman@uliege.be \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=noureddine@arista.com \
    --cc=pabeni@redhat.com \
    --cc=prestwoj@gmail.com \
    --cc=shuah@kernel.org \
    --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 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.