From: patchwork-bot+netdevbpf@kernel.org
To: Yumei Huang <yuhuang@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, sbrivio@redhat.com,
david@gibson.dropbear.id.au, davem@davemloft.net,
dsahern@kernel.org, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, justin.iurman@uliege.be,
shuah@kernel.org
Subject: Re: [PATCH net-next v2] ipv6: preserve insertion order for same-scope addresses
Date: Wed, 07 Jan 2026 01:00:09 +0000 [thread overview]
Message-ID: <176774760977.2183630.3799089848817482368.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260104032357.38555-1-yuhuang@redhat.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 4 Jan 2026 11:23:57 +0800 you wrote:
> IPv6 addresses with the same scope are returned in reverse insertion
> order, unlike IPv4. For example, when adding a -> b -> c, the list is
> reported as c -> b -> a, while IPv4 preserves the original order.
>
> This behavior causes:
>
> a. When using `ip -6 a save` and `ip -6 a restore`, addresses are restored
> in the opposite order from which they were saved. See example below
> showing addresses added as 1::1, 1::2, 1::3 but displayed and saved
> in reverse order.
>
> [...]
Here is the summary with links:
- [net-next,v2] ipv6: preserve insertion order for same-scope addresses
https://git.kernel.org/netdev/net-next/c/cb3de96eea66
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:[~2026-01-07 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 3:23 [PATCH net-next v2] ipv6: preserve insertion order for same-scope addresses Yumei Huang
2026-01-05 21:56 ` Justin Iurman
2026-01-06 17:37 ` David Ahern
2026-01-07 1:00 ` 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=176774760977.2183630.3799089848817482368.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=david@gibson.dropbear.id.au \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=justin.iurman@uliege.be \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbrivio@redhat.com \
--cc=shuah@kernel.org \
--cc=yuhuang@redhat.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