From: patchwork-bot+netdevbpf@kernel.org
To: Frank Wunderlich <linux@fw-web.de>
Cc: linux-usb@vger.kernel.org, frank-w@public-files.de,
bjorn@mork.no, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, johan@kernel.org,
gregkh@linuxfoundation.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add Support for Dell 5811e with usb-id 0x413c:0x81c2
Date: Tue, 27 Sep 2022 14:50:15 +0000 [thread overview]
Message-ID: <166429021565.22749.13023746895326673030.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220926150740.6684-1-linux@fw-web.de>
Hello:
This series was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 26 Sep 2022 17:07:38 +0200 you wrote:
> From: Frank Wunderlich <frank-w@public-files.de>
>
> Add new USB-id for dell branded EM7455 with this usb-id in qcserial and qmi
> driver.
> MBIM-mode works out of the box with 6.0-rc6.
>
> Frank Wunderlich (2):
> USB: serial: qcserial: add new usb-id for Dell branded EM7455
> net: usb: qmi_wwan: Add new usb-id for Dell branded EM7455
>
> [...]
Here is the summary with links:
- [1/2] USB: serial: qcserial: add new usb-id for Dell branded EM7455
(no matching commit)
- [2/2] net: usb: qmi_wwan: Add new usb-id for Dell branded EM7455
https://git.kernel.org/netdev/net/c/797666cd5af0
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-09-27 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 15:07 [PATCH 0/2] Add Support for Dell 5811e with usb-id 0x413c:0x81c2 Frank Wunderlich
2022-09-26 15:07 ` [PATCH 1/2] USB: serial: qcserial: add new usb-id for Dell branded EM7455 Frank Wunderlich
2022-09-27 6:31 ` Johan Hovold
2022-09-27 6:48 ` Aw: " Frank Wunderlich
2022-09-27 7:04 ` Johan Hovold
2022-09-26 15:07 ` [PATCH 2/2] net: usb: qmi_wwan: Add " Frank Wunderlich
2022-09-26 17:04 ` Bjørn Mork
2022-09-27 14: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=166429021565.22749.13023746895326673030.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=frank-w@public-files.de \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@fw-web.de \
--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).