From: patchwork-bot+netdevbpf@kernel.org
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>
Cc: linux-usb@vger.kernel.org, netdev@vger.kernel.org,
horms@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
o.rempel@pengutronix.de, ebiggers@google.com,
rmk+kernel@armlinux.org.uk, peter@korsgaard.com
Subject: Re: [PATCH net-next v3] net: usb: sr9700: remove code to drive nonexistent multicast filter
Date: Wed, 04 Feb 2026 03:50:22 +0000 [thread overview]
Message-ID: <177017702212.2171580.301972725500810661.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260203013924.28582-1-enelsonmoore@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 2 Feb 2026 17:39:09 -0800 you wrote:
> Several registers referenced in this driver's source code do not
> actually exist (they are not writable and read as zero in my testing).
> They exist in this driver because it originated as a copy of the dm9601
> driver. Notably, these include the multicast filter registers - this
> causes the driver to not support multicast packets correctly. Remove
> the multicast filter code and register definitions. Instead, set the
> chip to receive all multicast filter packets when any multicast
> addresses are in the list.
>
> [...]
Here is the summary with links:
- [net-next,v3] net: usb: sr9700: remove code to drive nonexistent multicast filter
https://git.kernel.org/netdev/net-next/c/9a9424c756fe
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-02-04 3:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 1:39 [PATCH net-next v3] net: usb: sr9700: remove code to drive nonexistent multicast filter Ethan Nelson-Moore
2026-02-04 3:43 ` Jakub Kicinski
2026-02-04 3:44 ` Jakub Kicinski
2026-02-04 3:46 ` Ethan Nelson-Moore
2026-02-04 3:54 ` Jakub Kicinski
2026-02-04 3:54 ` Ethan Nelson-Moore
2026-02-04 3:50 ` 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=177017702212.2171580.301972725500810661.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=ebiggers@google.com \
--cc=edumazet@google.com \
--cc=enelsonmoore@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=peter@korsgaard.com \
--cc=rmk+kernel@armlinux.org.uk \
/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