Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: matt@codeconstruct.com.au, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, gregkh@linuxfoundation.org,
	netdev@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH net-next v5 00/12] net: mctp: usb: Add support for MCTP-over-USB v1.1
Date: Fri, 31 Jul 2026 00:10:22 +0000	[thread overview]
Message-ID: <178545662289.51892.16997798956064212480.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260724-dev-mctp-usb-1-1-v5-0-e66bbba0dbdc@codeconstruct.com.au>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 24 Jul 2026 13:15:21 +0800 you wrote:
> Version 1.1.0 of DSP0283 (MCTP over USB transport binding) has been
> released, this patch series updates our current v1.0.1 support for the
> changes in v1.1.x.
> 
> The major change in v1.1 is the introduction of "packet spanning" mode,
> where a single MCTP packet may be split over multiple USB packets
> (themselves forming a single USB bulk transfer). This relaxes the
> requirement for USB high-speed mode, as we can now send MCTP packets
> contained over multiple 64-byte full-speed USB bulk transfers, and gives
> us an increase in the maximum MCTP packet size - we now have 13 bits of
> packet length (previously 8) in the transport header.
> 
> [...]

Here is the summary with links:
  - [net-next,v5,01/12] net: mctp: usb: Include version indicator in max packet size defines
    https://git.kernel.org/netdev/net-next/c/2f2e974f8fbe
  - [net-next,v5,02/12] net: mctp: usb: Use packet-length max for maximum packet-size check
    https://git.kernel.org/netdev/net-next/c/05b1a3a5eeaa
  - [net-next,v5,03/12] net: mctp: usblib: Move RX transfer processing to a new mctp-usblib
    https://git.kernel.org/netdev/net-next/c/b8564b19c0ff
  - [net-next,v5,04/12] net: mctp: usb: Improve IN endpoint status handling
    https://git.kernel.org/netdev/net-next/c/9f66be014070
  - [net-next,v5,05/12] net: mctp: usblib: Move TX transfer processing to mctp-usblib
    https://git.kernel.org/netdev/net-next/c/aadf5ed03e85
  - [net-next,v5,06/12] net: mctp: usblib: Add support for multi-packet transmit
    https://git.kernel.org/netdev/net-next/c/76a58ffd7417
  - [net-next,v5,07/12] net: mctp: usb: Accommodate DSP0283 v1.1 header format
    https://git.kernel.org/netdev/net-next/c/f5bf226f3c7a
  - [net-next,v5,08/12] net: mctp: usblib: Implement receive-side packet spanning
    https://git.kernel.org/netdev/net-next/c/d52fc7f09a18
  - [net-next,v5,09/12] net: mctp: usblib: Implement transmit-side packet spanning
    https://git.kernel.org/netdev/net-next/c/081ac93ca99c
  - [net-next,v5,10/12] net: mctp: usblib: Add initial kunit tests
    https://git.kernel.org/netdev/net-next/c/e84c0edbc41a
  - [net-next,v5,11/12] net: mctp: usb: enable v1.1 packet spanning
    https://git.kernel.org/netdev/net-next/c/b4a27a474b51
  - [net-next,v5,12/12] net: mctp: usb: Allow multiple urbs in flight
    https://git.kernel.org/netdev/net-next/c/88dbfe0d9581

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-07-31  0:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24  5:15 [PATCH net-next v5 00/12] net: mctp: usb: Add support for MCTP-over-USB v1.1 Jeremy Kerr
2026-07-24  5:15 ` [PATCH net-next v5 01/12] net: mctp: usb: Include version indicator in max packet size defines Jeremy Kerr
2026-07-24  5:15 ` [PATCH net-next v5 02/12] net: mctp: usb: Use packet-length max for maximum packet-size check Jeremy Kerr
2026-07-24  5:15 ` [PATCH net-next v5 03/12] net: mctp: usblib: Move RX transfer processing to a new mctp-usblib Jeremy Kerr
2026-07-24  5:15 ` [PATCH net-next v5 04/12] net: mctp: usb: Improve IN endpoint status handling Jeremy Kerr
2026-07-24  5:15 ` [PATCH net-next v5 05/12] net: mctp: usblib: Move TX transfer processing to mctp-usblib Jeremy Kerr
2026-07-24  5:15 ` [PATCH net-next v5 06/12] net: mctp: usblib: Add support for multi-packet transmit Jeremy Kerr
2026-07-24  5:15 ` [PATCH net-next v5 07/12] net: mctp: usb: Accommodate DSP0283 v1.1 header format Jeremy Kerr
2026-07-24  5:15 ` [PATCH net-next v5 08/12] net: mctp: usblib: Implement receive-side packet spanning Jeremy Kerr
2026-07-24  5:15 ` [PATCH net-next v5 09/12] net: mctp: usblib: Implement transmit-side " Jeremy Kerr
2026-07-24  5:15 ` [PATCH net-next v5 10/12] net: mctp: usblib: Add initial kunit tests Jeremy Kerr
2026-07-24  5:15 ` [PATCH net-next v5 11/12] net: mctp: usb: enable v1.1 packet spanning Jeremy Kerr
2026-07-24  5:15 ` [PATCH net-next v5 12/12] net: mctp: usb: Allow multiple urbs in flight Jeremy Kerr
2026-07-27  2:18 ` [PATCH net-next v5 00/12] net: mctp: usb: Add support for MCTP-over-USB v1.1 Jeremy Kerr
2026-07-31  0:10 ` 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=178545662289.51892.16997798956064212480.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 \
    /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