From: patchwork-bot+netdevbpf@kernel.org
To: Sven van Ashbrook <svenva@chromium.org>
Cc: linux-kernel@vger.kernel.org, levinale@google.com,
chithraa@google.com, frankgor@google.com, aaron.ma@canonical.com,
dober6023@gmail.com, davem@davemloft.net, edumazet@google.com,
chenhao288@hisilicon.com, hayeswang@realtek.com, kuba@kernel.org,
jflf_kernel@gmx.com, pabeni@redhat.com,
linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v1] r8152: allow userland to disable multicast
Date: Wed, 31 Aug 2022 22:00:17 +0000 [thread overview]
Message-ID: <166198321700.20200.2886724035407277786.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220830045923.net-next.v1.1.I4fee0ac057083d4f848caf0fa3a9fd466fc374a0@changeid>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 30 Aug 2022 04:59:39 +0000 you wrote:
> The rtl8152 driver does not disable multicasting when userspace asks
> it to. For example:
> $ ifconfig eth0 -multicast -allmulti
> $ tcpdump -p -i eth0 # will still capture multicast frames
>
> Fix by clearing the device multicast filter table when multicast and
> allmulti are both unset.
>
> [...]
Here is the summary with links:
- [net-next,v1] r8152: allow userland to disable multicast
https://git.kernel.org/netdev/net-next/c/7305b78ae45f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-08-31 22:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 4:59 [PATCH net-next v1] r8152: allow userland to disable multicast Sven van Ashbrook
2022-08-31 3:14 ` Hayes Wang
2022-08-31 22:00 ` patchwork-bot+netdevbpf [this message]
2022-08-31 22:32 ` Sven van Ashbrook
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=166198321700.20200.2886724035407277786.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aaron.ma@canonical.com \
--cc=chenhao288@hisilicon.com \
--cc=chithraa@google.com \
--cc=davem@davemloft.net \
--cc=dober6023@gmail.com \
--cc=edumazet@google.com \
--cc=frankgor@google.com \
--cc=hayeswang@realtek.com \
--cc=jflf_kernel@gmx.com \
--cc=kuba@kernel.org \
--cc=levinale@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=svenva@chromium.org \
/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).