From: patchwork-bot+netdevbpf@kernel.org
To: Hector Martin <marcan@marcan.st>
Cc: jackychou@asix.com.tw, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] net: usb: ax88179_178a: Bind only to vendor-specific interface
Date: Tue, 02 Aug 2022 11:00:13 +0000 [thread overview]
Message-ID: <165943801356.21664.8346442629133964190.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220731072209.45504-1-marcan@marcan.st>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 31 Jul 2022 16:22:09 +0900 you wrote:
> The Anker PowerExpand USB-C to Gigabit Ethernet adapter uses this
> chipset, but exposes CDC Ethernet configurations as well as the
> vendor specific one. This driver tries to bind by PID:VID
> unconditionally and ends up picking up the CDC configuration, which
> is supposed to be handled by the class driver. To make things even
> more confusing, it sees both of the CDC class interfaces and tries
> to bind twice, resulting in two broken Ethernet devices.
>
> [...]
Here is the summary with links:
- [v4] net: usb: ax88179_178a: Bind only to vendor-specific interface
https://git.kernel.org/netdev/net/c/c67cc4315a8e
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-08-02 11:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 7:22 [PATCH v4] net: usb: ax88179_178a: Bind only to vendor-specific interface Hector Martin
2022-08-02 11:00 ` 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=165943801356.21664.8346442629133964190.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jackychou@asix.com.tw \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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).