From: patchwork-bot+netdevbpf@kernel.org
To: Kalash Nainwal <kalash@arista.com>
Cc: netdev@vger.kernel.org, fruggeri@arista.com, dsahern@gmail.com,
davem@davemloft.net, yoshfuji@linux-ipv6.org, dsahern@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Generate netlink notification when default IPv6 route preference changes
Date: Mon, 14 Feb 2022 11:20:10 +0000 [thread overview]
Message-ID: <164483761062.10850.8641197863341390379.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220210220935.21139-1-kalash@arista.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 10 Feb 2022 14:09:35 -0800 you wrote:
> Generate RTM_NEWROUTE netlink notification when the route preference
> changes on an existing kernel generated default route in response to
> RA messages. Currently netlink notifications are generated only when
> this route is added or deleted but not when the route preference
> changes, which can cause userspace routing application state to go
> out of sync with kernel.
>
> [...]
Here is the summary with links:
- [v2] Generate netlink notification when default IPv6 route preference changes
https://git.kernel.org/netdev/net-next/c/806c37ddcf28
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-02-14 11:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 22:09 [PATCH v2] Generate netlink notification when default IPv6 route preference changes Kalash Nainwal
2022-02-12 19:32 ` David Ahern
2022-02-14 11:20 ` 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=164483761062.10850.8641197863341390379.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--cc=fruggeri@arista.com \
--cc=kalash@arista.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox