From: patchwork-bot+netdevbpf@kernel.org
To: Yuyang Huang <yuyanghuang@google.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, dsahern@kernel.org,
netdev@vger.kernel.org, bluca@debian.org, maze@google.com,
lorenzo@google.com, bugs.a.b@free.fr
Subject: Re: [PATCH iproute2] iproute2: bugfix - restore ip monitor backward compatibility.
Date: Mon, 26 May 2025 15:20:37 +0000 [thread overview]
Message-ID: <174827283774.956475.16588266056869229481.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250523032518.251497-1-yuyanghuang@google.com>
Hello:
This patch was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Fri, 23 May 2025 12:25:18 +0900 you wrote:
> The current ip monitor implementation fails on older kernels that lack
> newer RTNLGRP_* definitions. As ip monitor is expected to maintain
> backward compatibility, this commit updates the code to check if errno
> is not EINVAL when rtnl_add_nl_group() fails. This change restores ip
> monitor's backward compatibility with older kernel versions.
>
> Cc: David Ahern <dsahern@kernel.org>
> Cc: Luca Boccassi <bluca@debian.org>
> Cc: Maciej Żenczykowski <maze@google.com>
> Cc: Lorenzo Colitti <lorenzo@google.com>
> Reported-by: Adel Belhouane <bugs.a.b@free.fr>
> Closes: https://lore.kernel.org/netdev/CADXeF1GgJ_1tee3hc7gca2Z21Lyi3mzxq52sSfMg3mFQd2rGWQ@mail.gmail.com/T/#t
> Signed-off-by: Yuyang Huang <yuyanghuang@google.com>
>
> [...]
Here is the summary with links:
- [iproute2] iproute2: bugfix - restore ip monitor backward compatibility.
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=969817ce1ddb
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:[~2025-05-26 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-23 3:25 [PATCH iproute2] iproute2: bugfix - restore ip monitor backward compatibility Yuyang Huang
2025-05-23 10:25 ` Luca Boccassi
2025-05-26 15: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=174827283774.956475.16588266056869229481.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bluca@debian.org \
--cc=bugs.a.b@free.fr \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lorenzo@google.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yuyanghuang@google.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).