From: patchwork-bot+netdevbpf@kernel.org
To: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 v2 0/2]
Date: Mon, 16 Nov 2026 18:00:09 +0000 [thread overview]
Message-ID: <179485200952.3802119.16560123532175308493.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261116111613.25820-1-dev.kurt@vandijck-laurijssen.be>
Hello:
This series was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Mon, 16 Nov 2026 12:09:37 +0100 you wrote:
> Current implementation of address protocols in iproute2 allow to add
> them, and iproute2 will show them, but you cannot use them to really filter.
> These 2 patches fix 2 shortcomings of current iproute2's 'proto' parameter
> handling:
> 1/2: allow to use labels from rt_addrprotos tables
> 2/2: treat addresses with no addrproto as PROTO_UNSPEC
>
> [...]
Here is the summary with links:
- [iproute2,1/2] ip address: allow labeled proto arguments
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=e7ea8f74e81a
- [iproute2,2/2] ip address: proto filters rejects items without proto
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=75fc1c7d6d19
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-11-16 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 11:09 [PATCH iproute2 v2 0/2] Kurt Van Dijck
2026-11-16 11:09 ` [PATCH iproute2 1/2] ip address: allow labeled proto arguments Kurt Van Dijck
2026-11-16 11:09 ` [PATCH iproute2 2/2] ip address: proto filters rejects items without proto Kurt Van Dijck
2026-11-16 18: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=179485200952.3802119.16560123532175308493.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dev.kurt@vandijck-laurijssen.be \
--cc=netdev@vger.kernel.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