All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Matt Johnston <matt@codeconstruct.com.au>
Cc: linux-i3c@lists.infradead.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, edumazet@google.com, jk@codeconstruct.com.au,
	alexandre.belloni@bootlin.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	miquel.raynal@bootlin.com
Subject: Re: [PATCH net-next v6 0/3] I3C MCTP net driver
Date: Tue, 17 Oct 2023 11:00:24 +0000	[thread overview]
Message-ID: <169754042417.23145.5070726957751164458.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231013040628.354323-1-matt@codeconstruct.com.au>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 13 Oct 2023 12:06:22 +0800 you wrote:
> This series adds an I3C transport for the kernel's MCTP network
> protocol. MCTP is a communication protocol between system components
> (BMCs, drives, NICs etc), with higher level protocols such as NVMe-MI or
> PLDM built on top of it (in userspace). It runs over various transports
> such as I2C, PCIe, or I3C.
> 
> The mctp-i3c driver follows a similar approach to the kernel's existing
> mctp-i2c driver, creating a "mctpi3cX" network interface for each
> numbered I3C bus. Busses opt in to support by adding a "mctp-controller"
> property to the devicetree:
> 
> [...]

Here is the summary with links:
  - [net-next,v6,1/3] dt-bindings: i3c: Add mctp-controller property
    https://git.kernel.org/netdev/net-next/c/ee71d6d5f18b
  - [net-next,v6,2/3] i3c: Add support for bus enumeration & notification
    https://git.kernel.org/netdev/net-next/c/0ac6486e5cbd
  - [net-next,v6,3/3] mctp i3c: MCTP I3C driver
    https://git.kernel.org/netdev/net-next/c/c8755b29b58e

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



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Matt Johnston <matt@codeconstruct.com.au>
Cc: linux-i3c@lists.infradead.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, edumazet@google.com, jk@codeconstruct.com.au,
	alexandre.belloni@bootlin.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	miquel.raynal@bootlin.com
Subject: Re: [PATCH net-next v6 0/3] I3C MCTP net driver
Date: Tue, 17 Oct 2023 11:00:24 +0000	[thread overview]
Message-ID: <169754042417.23145.5070726957751164458.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231013040628.354323-1-matt@codeconstruct.com.au>

Hello:

This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 13 Oct 2023 12:06:22 +0800 you wrote:
> This series adds an I3C transport for the kernel's MCTP network
> protocol. MCTP is a communication protocol between system components
> (BMCs, drives, NICs etc), with higher level protocols such as NVMe-MI or
> PLDM built on top of it (in userspace). It runs over various transports
> such as I2C, PCIe, or I3C.
> 
> The mctp-i3c driver follows a similar approach to the kernel's existing
> mctp-i2c driver, creating a "mctpi3cX" network interface for each
> numbered I3C bus. Busses opt in to support by adding a "mctp-controller"
> property to the devicetree:
> 
> [...]

Here is the summary with links:
  - [net-next,v6,1/3] dt-bindings: i3c: Add mctp-controller property
    https://git.kernel.org/netdev/net-next/c/ee71d6d5f18b
  - [net-next,v6,2/3] i3c: Add support for bus enumeration & notification
    https://git.kernel.org/netdev/net-next/c/0ac6486e5cbd
  - [net-next,v6,3/3] mctp i3c: MCTP I3C driver
    https://git.kernel.org/netdev/net-next/c/c8755b29b58e

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



-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  parent reply	other threads:[~2023-10-17 11:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13  4:06 [PATCH net-next v6 0/3] I3C MCTP net driver Matt Johnston
2023-10-13  4:06 ` Matt Johnston
2023-10-13  4:06 ` [PATCH net-next v6 1/3] dt-bindings: i3c: Add mctp-controller property Matt Johnston
2023-10-13  4:06   ` Matt Johnston
2023-10-13  4:06 ` [PATCH net-next v6 2/3] i3c: Add support for bus enumeration & notification Matt Johnston
2023-10-13  4:06   ` Matt Johnston
2023-10-13  4:06 ` [PATCH net-next v6 3/3] mctp i3c: MCTP I3C driver Matt Johnston
2023-10-13  4:06   ` Matt Johnston
2023-10-17  8:24   ` Simon Horman
2023-10-17  8:24     ` Simon Horman
2023-10-17 10:46     ` Paolo Abeni
2023-10-17 10:46       ` Paolo Abeni
2023-10-17 11:00 ` patchwork-bot+netdevbpf [this message]
2023-10-17 11:00   ` [PATCH net-next v6 0/3] I3C MCTP net driver patchwork-bot+netdevbpf

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=169754042417.23145.5070726957751164458.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=jk@codeconstruct.com.au \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-i3c@lists.infradead.org \
    --cc=matt@codeconstruct.com.au \
    --cc=miquel.raynal@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.