From: patchwork-bot+netdevbpf@kernel.org
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: matt@codeconstruct.com.au, gregkh@linuxfoundation.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, spuranik@nvidia.com
Subject: Re: [PATCH net-next v3 0/2] mctp: Add MCTP-over-USB hardware transport binding
Date: Sat, 22 Feb 2025 03:30:41 +0000 [thread overview]
Message-ID: <174019504120.2279798.1941572582766631045.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250221-dev-mctp-usb-v3-0-3353030fe9cc@codeconstruct.com.au>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 21 Feb 2025 08:56:56 +0800 you wrote:
> Add an implementation of the DMTF standard DSP0283, providing an MCTP
> channel over high-speed USB.
>
> This is a fairly trivial first implementation, in that we only submit
> one tx and one rx URB at a time. We do accept multi-packet transfers,
> but do not yet generate them on transmit.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] usb: Add base USB MCTP definitions
https://git.kernel.org/netdev/net-next/c/dcc35baae732
- [net-next,v3,2/2] net: mctp: Add MCTP USB transport driver
https://git.kernel.org/netdev/net-next/c/0791c0327a6e
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:[~2025-02-22 3:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 0:56 [PATCH net-next v3 0/2] mctp: Add MCTP-over-USB hardware transport binding Jeremy Kerr
2025-02-21 0:56 ` [PATCH net-next v3 1/2] usb: Add base USB MCTP definitions Jeremy Kerr
2025-02-21 0:56 ` [PATCH net-next v3 2/2] net: mctp: Add MCTP USB transport driver Jeremy Kerr
2025-02-22 3:30 ` 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=174019504120.2279798.1941572582766631045.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=spuranik@nvidia.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