From: patchwork-bot+netdevbpf@kernel•org
To: Hangbin Liu <liuhangbin@gmail•com>
Cc: netdev@vger•kernel.org, davem@davemloft•net, dsahern@kernel•org,
edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
idosch@idosch•org
Subject: Re: [PATCHv7 net-next 0/2] ipv6: update route when delete source address
Date: Sun, 20 Aug 2023 18:13:29 +0000 [thread overview]
Message-ID: <169255520987.4244.9366813628919644122.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230818082902.1972738-1-liuhangbin@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft•net>:
On Fri, 18 Aug 2023 16:29:00 +0800 you wrote:
> Currently, when remove an address, the IPv6 route will not remove the
> prefer source address when the address is bond to other device. Fix this
> issue and add related tests as Ido and David suggested.
>
> Hangbin Liu (2):
> ipv6: do not match device when remove source route
> selftests: fib_test: add a test case for IPv6 source address delete
>
> [...]
Here is the summary with links:
- [PATCHv7,net-next,1/2] ipv6: do not match device when remove source route
https://git.kernel.org/netdev/net-next/c/b358f57f7db6
- [PATCHv7,net-next,2/2] selftests: fib_test: add a test case for IPv6 source address delete
https://git.kernel.org/netdev/net-next/c/429b55b441f3
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-08-20 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 8:29 [PATCHv7 net-next 0/2] ipv6: update route when delete source address Hangbin Liu
2023-08-18 8:29 ` [PATCHv7 net-next 1/2] ipv6: do not match device when remove source route Hangbin Liu
2023-08-19 0:28 ` David Ahern
2023-08-18 8:29 ` [PATCHv7 net-next 2/2] selftests: fib_test: add a test case for IPv6 source address delete Hangbin Liu
2023-08-19 0:31 ` David Ahern
2023-08-19 15:14 ` Ido Schimmel
2023-08-20 18:13 ` 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=169255520987.4244.9366813628919644122.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=idosch@idosch$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=liuhangbin@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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