From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Santiago_Ruano_Rinc=C3=B3n_=3Csantiago=2Eruano-rincon=40imt-atlant?=@ci.codeaurora.org,
=?utf-8?q?ique=2Efr=3E?=@ci.codeaurora.org
Cc: gregkh@linuxfoundation.org, oliver@neukum.org,
linux-usb@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2] net/cdc_ncm: Fix multicast RX support for CDC NCM devices with ZLP
Date: Wed, 23 Nov 2022 13:50:15 +0000 [thread overview]
Message-ID: <166921141535.13791.14050518206893569028.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221121205304.62587-1-santiago.ruano-rincon@imt-atlantique.fr>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 21 Nov 2022 21:53:05 +0100 you wrote:
> ZLP for DisplayLink ethernet devices was enabled in 6.0:
> 266c0190aee3 ("net/cdc_ncm: Enable ZLP for DisplayLink ethernet devices").
> The related driver_info should be the "same as cdc_ncm_info, but with
> FLAG_SEND_ZLP". However, set_rx_mode that enables handling multicast
> traffic was missing in the new cdc_ncm_zlp_info.
>
> usbnet_cdc_update_filter rx mode was introduced in linux 5.9 with:
> e10dcb1b6ba7 ("net: cdc_ncm: hook into set_rx_mode to admit multicast
> traffic")
>
> [...]
Here is the summary with links:
- [v2] net/cdc_ncm: Fix multicast RX support for CDC NCM devices with ZLP
https://git.kernel.org/netdev/net/c/748064b54c99
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:[~2022-11-23 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 13:13 [PATCH] net/cdc_ncm: Fix multicast RX support for CDC NCM devices with ZLP Santiago Ruano Rincón
2022-11-21 15:19 ` Greg KH
2022-11-21 15:45 ` Santiago Ruano Rincón
2022-11-21 18:13 ` Greg KH
2022-11-21 20:53 ` [PATCH v2] " Santiago Ruano Rincón
2022-11-23 13: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=166921141535.13791.14050518206893569028.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Santiago_Ruano_Rinc=C3=B3n_=3Csantiago=2Eruano-rincon=40imt-atlant?=@ci.codeaurora.org \
--cc==?utf-8?q?ique=2Efr=3E?=@ci.codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.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).