From: Jakub Kicinski <kuba@kernel•org>
To: Yuyang Huang <yuyanghuang@google•com>
Cc: "David S. Miller" <davem@davemloft•net>,
"Eric Dumazet" <edumazet@google•com>,
"Paolo Abeni" <pabeni@redhat•com>,
"Simon Horman" <horms@kernel•org>,
"David Ahern" <dsahern@kernel•org>,
roopa@cumulusnetworks•com, jiri@resnulli•us,
stephen@networkplumber•org, jimictw@google•com, prohr@google•com,
liuhangbin@gmail•com, nicolas.dichtel@6wind•com, andrew@lunn•ch,
pruddy@vyatta•att-mail.com, netdev@vger•kernel.org,
"Maciej Żenczykowski" <maze@google•com>,
"Lorenzo Colitti" <lorenzo@google•com>
Subject: Re: [PATCH net-next, v3] netlink: support dumping IPv4 multicast addresses
Date: Mon, 23 Dec 2024 10:25:12 -0800 [thread overview]
Message-ID: <20241223102512.68467ea3@kernel.org> (raw)
In-Reply-To: <20241221063522.1839126-1-yuyanghuang@google.com>
On Sat, 21 Dec 2024 15:35:22 +0900 Yuyang Huang wrote:
> Extended RTM_GETMULTICAST to support dumping joined IPv4 multicast
> addresses, in addition to the existing IPv6 functionality. This allows
> userspace applications to retrieve both IPv4 and IPv6 multicast
> addresses through similar netlink command and then monitor future
> changes by registering to RTNLGRP_IPV4_MCADDR and RTNLGRP_IPV6_MCADDR.
## Form letter - winter-break
Networking development is suspended for winter holidays, until Jan 2nd.
We are currently accepting bug fixes only, see the announcements at:
https://lore.kernel.org/20241211164022.6a075d3a@kernel.org
https://lore.kernel.org/20241220182851.7acb6416@kernel.org
RFC patches sent for review only are welcome at any time.
--
pw-bot: defer
pv-bot: closed
prev parent reply other threads:[~2024-12-23 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 6:35 [PATCH net-next, v3] netlink: support dumping IPv4 multicast addresses Yuyang Huang
2024-12-23 18:25 ` Jakub Kicinski [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=20241223102512.68467ea3@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=jimictw@google$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=liuhangbin@gmail$(echo .)com \
--cc=lorenzo@google$(echo .)com \
--cc=maze@google$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nicolas.dichtel@6wind$(echo .)com \
--cc=pabeni@redhat$(echo .)com \
--cc=prohr@google$(echo .)com \
--cc=pruddy@vyatta$(echo .)att-mail.com \
--cc=roopa@cumulusnetworks$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
--cc=yuyanghuang@google$(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