From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?QmrDuHJuIE1vcmsgPGJqb3JuQG1vcmsubm8+?=@ci.codeaurora.org
Cc: netdev@vger.kernel.org, hayeswang@realtek.com,
linux-usb@vger.kernel.org, oliver@neukum.org
Subject: Re: [PATCH 0/2] r8152: allow firmwares with NCM support
Date: Mon, 09 Jan 2023 07:50:16 +0000 [thread overview]
Message-ID: <167325061640.1839.15796258098196650486.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230106160739.100708-1-bjorn@mork.no>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 6 Jan 2023 17:07:37 +0100 you wrote:
> Some device and firmware combinations with NCM support will
> end up using the cdc_ncm driver by default. This is sub-
> optimal for the same reasons we've previously accepted the
> blacklist hack in cdc_ether.
>
> The recent support for subclassing the generic USB device
> driver allows us to create a very slim driver with the same
> functionality. This patch set uses that to implement a
> device specific configuration default which is independent
> of any USB interface drivers. This means that it works
> equally whether the device initially ends up in NCM or ECM
> mode, without depending on any code in the respective class
> drivers.
>
> [...]
Here is the summary with links:
- [1/2] r8152: add USB device driver for config selection
https://git.kernel.org/netdev/net-next/c/ec51fbd1b8a2
- [2/2] cdc_ether: no need to blacklist any r8152 devices
https://git.kernel.org/netdev/net-next/c/69649ef84053
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:[~2023-01-09 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 16:07 [PATCH 0/2] r8152: allow firmwares with NCM support Bjørn Mork
2023-01-06 16:07 ` [PATCH 1/2] r8152: add USB device driver for config selection Bjørn Mork
2023-01-06 16:07 ` [PATCH 2/2] cdc_ether: no need to blacklist any r8152 devices Bjørn Mork
2023-01-09 7:50 ` patchwork-bot+netdevbpf [this message]
2023-03-04 10:00 ` [PATCH 0/2] r8152: allow firmwares with NCM support Juhyung Park
2023-03-06 7:19 ` Greg KH
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=167325061640.1839.15796258098196650486.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?QmrDuHJuIE1vcmsgPGJqb3JuQG1vcmsubm8+?=@ci.codeaurora.org \
--cc=hayeswang@realtek.com \
--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).