Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yuyang Huang <sigefriedhyy@gmail.com>
Cc: davem@davemloft.net, andrew+netdev@lunn.ch, dsahern@kernel.org,
	donald.hunter@gmail.com, edumazet@google.com, idosch@nvidia.com,
	kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
	horms@kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] net: report multicast group user count
Date: Fri, 03 Jul 2026 07:00:15 +0000	[thread overview]
Message-ID: <178306201573.2494164.11397995719215578269.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260630110207.37841-1-sigefriedhyy@gmail.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue, 30 Jun 2026 20:02:04 +0900 you wrote:
> RTM_GETMULTICAST reports IPv4 and IPv6 multicast group membership, but
> does not include the per-group user count. Userspace therefore still has
> to parse /proc/net/igmp and /proc/net/igmp6 to obtain the Users column.
> In particular, this prevents iproute2 from moving "ip maddr show"
> entirely from procfs to rtnetlink.
> 
> Add IFA_MC_USERS to carry the user count in RTM_GETMULTICAST dumps and
> RTM_NEWMULTICAST / RTM_DELMULTICAST notifications for both address
> families. Update the rt-addr YNL specification and extend the rtnetlink
> selftest to verify that two joins increase the reported count by two.
> 
> [...]

Here is the summary with links:
  - [net-next,1/3] net: ipv4: report multicast group user count
    https://git.kernel.org/netdev/net-next/c/7cb8198761e6
  - [net-next,2/3] net: ipv6: report multicast group user count
    https://git.kernel.org/netdev/net-next/c/e1d0f3f08391
  - [net-next,3/3] selftests: net: check multicast group user count
    https://git.kernel.org/netdev/net-next/c/3373cb099e66

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-07-03  7:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 11:02 [PATCH net-next 0/3] net: report multicast group user count Yuyang Huang
2026-06-30 11:02 ` [PATCH net-next 1/3] net: ipv4: " Yuyang Huang
2026-07-01 20:54   ` Vadim Fedorenko
2026-07-02  8:11   ` Ido Schimmel
2026-06-30 11:02 ` [PATCH net-next 2/3] net: ipv6: " Yuyang Huang
2026-07-01 20:55   ` Vadim Fedorenko
2026-07-02  8:12   ` Ido Schimmel
2026-06-30 11:02 ` [PATCH net-next 3/3] selftests: net: check " Yuyang Huang
2026-07-01 20:55   ` Vadim Fedorenko
2026-07-03  6:50 ` [PATCH net-next 0/3] net: report " Paolo Abeni
2026-07-03  6:52   ` Yuyang Huang
2026-07-03  7: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=178306201573.2494164.11397995719215578269.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --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=shuah@kernel.org \
    --cc=sigefriedhyy@gmail.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