From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, dsahern@kernel.org,
mark.tomlinson@alliedtelesis.co.nz, sharpd@nvidia.com,
mlxsw@nvidia.com
Subject: Re: [PATCH net 0/2] ipv4: Two bug fixes
Date: Wed, 07 Dec 2022 04:40:16 +0000 [thread overview]
Message-ID: <167038801639.19727.8599688624920791761.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221204075045.3780097-1-idosch@nvidia.com>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 4 Dec 2022 09:50:43 +0200 you wrote:
> Two small fixes for bugs in IPv4 routing code.
>
> A variation of the second bug was reported by an FRR 5.0 (released
> 06/18) user as this version was setting a table ID of 0 for the default
> VRF, unlike iproute2 and newer FRR versions.
>
> The first bug was discovered while fixing the second.
>
> [...]
Here is the summary with links:
- [net,1/2] ipv4: Fix incorrect route flushing when source address is deleted
https://git.kernel.org/netdev/net/c/f96a3d74554d
- [net,2/2] ipv4: Fix incorrect route flushing when table ID 0 is used
https://git.kernel.org/netdev/net/c/c0d999348e01
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-12-07 4:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 7:50 [PATCH net 0/2] ipv4: Two bug fixes Ido Schimmel
2022-12-04 7:50 ` [PATCH net 1/2] ipv4: Fix incorrect route flushing when source address is deleted Ido Schimmel
2022-12-04 16:25 ` David Ahern
2022-12-04 7:50 ` [PATCH net 2/2] ipv4: Fix incorrect route flushing when table ID 0 is used Ido Schimmel
2022-12-04 16:27 ` David Ahern
2022-12-07 4: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=167038801639.19727.8599688624920791761.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mark.tomlinson@alliedtelesis.co.nz \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sharpd@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).