From: patchwork-bot+netdevbpf@kernel.org
To: Patrick Rohr <prohr@google.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, maze@google.com,
lorenzo@google.com, dsahern@kernel.org
Subject: Re: [net-next v2] net: change accept_ra_min_rtr_lft to affect all RA lifetimes
Date: Fri, 28 Jul 2023 20:40:24 +0000 [thread overview]
Message-ID: <169057682463.20429.934464089446215537.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230726230701.919212-1-prohr@google.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 26 Jul 2023 16:07:01 -0700 you wrote:
> accept_ra_min_rtr_lft only considered the lifetime of the default route
> and discarded entire RAs accordingly.
>
> This change renames accept_ra_min_rtr_lft to accept_ra_min_lft, and
> applies the value to individual RA sections; in particular, router
> lifetime, PIO preferred lifetime, and RIO lifetime. If any of those
> lifetimes are lower than the configured value, the specific RA section
> is ignored.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: change accept_ra_min_rtr_lft to affect all RA lifetimes
https://git.kernel.org/netdev/net-next/c/5027d54a9c30
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:[~2023-07-28 20:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 23:07 [net-next v2] net: change accept_ra_min_rtr_lft to affect all RA lifetimes Patrick Rohr
2023-07-27 12:23 ` Simon Horman
2023-07-27 12:38 ` Maciej Żenczykowski
2023-07-27 12:45 ` Simon Horman
2023-07-27 12:51 ` Maciej Żenczykowski
2023-07-27 15:24 ` David Ahern
2023-07-28 20:32 ` Jakub Kicinski
2023-07-28 20:40 ` 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=169057682463.20429.934464089446215537.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=lorenzo@google.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--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.