From: patchwork-bot+netdevbpf@kernel.org
To: Ujjal Roy <royujjal@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, razor@blackwall.org,
idosch@nvidia.com, dsahern@kernel.org, shuah@kernel.org,
aroulin@nvidia.com, yongwang@nvidia.com, petrm@nvidia.com,
ujjal@alumnux.com, bridge@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v6 0/5] net: bridge: mcast: support exponential field encoding
Date: Tue, 05 May 2026 02:20:26 +0000 [thread overview]
Message-ID: <177794762679.1391894.7351753363861517582.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260502131907.987-1-royujjal@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 2 May 2026 13:19:01 +0000 you wrote:
> Description:
> This series addresses a mismatch in how multicast query
> intervals and response codes are handled across IPv4 (IGMPv3)
> and IPv6 (MLDv2). While decoding logic currently exists,
> the corresponding encoding logic is missing during query
> packet generation. This leads to incorrect intervals being
> transmitted when values exceed their linear thresholds.
>
> [...]
Here is the summary with links:
- [net-next,v6,1/5] ipv4: igmp: get rid of IGMPV3_{QQIC,MRC} and simplify calculation
https://git.kernel.org/netdev/net-next/c/726fa7da2d8c
- [net-next,v6,2/5] ipv6: mld: rename mldv2_mrc() and add mldv2_qqi()
https://git.kernel.org/netdev/net-next/c/12cfb4ecc471
- [net-next,v6,3/5] ipv4: igmp: encode multicast exponential fields
https://git.kernel.org/netdev/net-next/c/95bfd196f0dc
- [net-next,v6,4/5] ipv6: mld: encode multicast exponential fields
https://git.kernel.org/netdev/net-next/c/e51560f4220a
- [net-next,v6,5/5] selftests: net: bridge: add MRC and QQIC field encoding tests
https://git.kernel.org/netdev/net-next/c/529dbe762de0
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-05-05 2:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-02 13:19 [PATCH net-next v6 0/5] net: bridge: mcast: support exponential field encoding Ujjal Roy
2026-05-02 13:19 ` [PATCH net-next v6 1/5] ipv4: igmp: get rid of IGMPV3_{QQIC,MRC} and simplify calculation Ujjal Roy
2026-05-02 13:19 ` [PATCH net-next v6 2/5] ipv6: mld: rename mldv2_mrc() and add mldv2_qqi() Ujjal Roy
2026-05-02 13:19 ` [PATCH net-next v6 3/5] ipv4: igmp: encode multicast exponential fields Ujjal Roy
2026-05-02 13:19 ` [PATCH net-next v6 4/5] ipv6: mld: " Ujjal Roy
2026-05-02 13:19 ` [PATCH net-next v6 5/5] selftests: net: bridge: add MRC and QQIC field encoding tests Ujjal Roy
2026-05-05 2:09 ` [PATCH net-next v6 0/5] net: bridge: mcast: support exponential field encoding Jakub Kicinski
2026-05-05 2: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=177794762679.1391894.7351753363861517582.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aroulin@nvidia.com \
--cc=bridge@lists.linux.dev \
--cc=davem@davemloft.net \
--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=petrm@nvidia.com \
--cc=razor@blackwall.org \
--cc=royujjal@gmail.com \
--cc=shuah@kernel.org \
--cc=ujjal@alumnux.com \
--cc=yongwang@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.