All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Matt Johnston <matt@codeconstruct.com.au>
Cc: zev@bewilderbeest.net, wsa@kernel.org, robh+dt@kernel.org,
	davem@davemloft.net, kuba@kernel.org, brendanhiggins@google.com,
	benh@kernel.crashing.org, joel@jms.id.au, andrew@aj.id.au,
	avifishman70@gmail.com, tmaimon77@gmail.com,
	tali.perry1@gmail.com, venture@google.com, yuenn@google.com,
	benjaminfair@google.com, jk@codeconstruct.com.au,
	linux-i2c@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/6] MCTP I2C driver
Date: Mon, 15 Nov 2021 14:20:11 +0000	[thread overview]
Message-ID: <163698601142.19991.3686735228078461111.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211115024926.205385-1-matt@codeconstruct.com.au>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Mon, 15 Nov 2021 10:49:20 +0800 you wrote:
> Hi,
> 
> This patch series adds a netdev driver providing MCTP transport over
> I2C.
> 
> It applies against net-next using recent MCTP changes there, though also
> has I2C core changes for review. I'll leave it to maintainers where it
> should be applied - please let me know if it needs to be submitted
> differently.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/6] i2c: core: Allow 255 byte transfers for SMBus 3.x
    https://git.kernel.org/netdev/net-next/c/13cae4a104d2
  - [net-next,v3,2/6] i2c: dev: Handle 255 byte blocks for i2c ioctl
    https://git.kernel.org/netdev/net-next/c/84a107e68b34
  - [net-next,v3,3/6] i2c: aspeed: Allow 255 byte block transfers
    https://git.kernel.org/netdev/net-next/c/1b2ba1f591c9
  - [net-next,v3,4/6] i2c: npcm7xx: Allow 255 byte block SMBus transfers
    https://git.kernel.org/netdev/net-next/c/3ef2de27a05a
  - [net-next,v3,5/6] dt-bindings: net: New binding mctp-i2c-controller
    https://git.kernel.org/netdev/net-next/c/0b6141eb2b14
  - [net-next,v3,6/6] mctp i2c: MCTP I2C binding driver
    https://git.kernel.org/netdev/net-next/c/80be9b2c0d93

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



  parent reply	other threads:[~2021-11-15 14:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15  2:49 [PATCH net-next v3 0/6] MCTP I2C driver Matt Johnston
2021-11-15  2:49 ` [PATCH net-next v3 1/6] i2c: core: Allow 255 byte transfers for SMBus 3.x Matt Johnston
2021-11-15  2:49 ` [PATCH net-next v3 2/6] i2c: dev: Handle 255 byte blocks for i2c ioctl Matt Johnston
2021-11-25  6:00   ` [PATCH] i2c: dev: fix eno.cocci warnings kernel test robot
2021-11-25  6:03   ` [PATCH net-next v3 2/6] i2c: dev: Handle 255 byte blocks for i2c ioctl kernel test robot
2021-11-15  2:49 ` [PATCH net-next v3 3/6] i2c: aspeed: Allow 255 byte block transfers Matt Johnston
2021-11-15  2:49 ` [PATCH net-next v3 4/6] i2c: npcm7xx: Allow 255 byte block SMBus transfers Matt Johnston
2021-11-15  2:49 ` [PATCH net-next v3 5/6] dt-bindings: net: New binding mctp-i2c-controller Matt Johnston
2021-11-15  2:49 ` [PATCH net-next v3 6/6] mctp i2c: MCTP I2C binding driver Matt Johnston
2021-11-15 14:20 ` patchwork-bot+netdevbpf [this message]
2021-11-15 15:30   ` [PATCH net-next v3 0/6] MCTP I2C driver Wolfram Sang
2021-11-15 16:08     ` Jakub Kicinski
2021-11-15 16:11       ` Wolfram Sang
2021-11-24  3:15     ` Matt Johnston
2021-11-29 19:34       ` Wolfram Sang

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=163698601142.19991.3686735228078461111.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@aj.id.au \
    --cc=avifishman70@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=benjaminfair@google.com \
    --cc=brendanhiggins@google.com \
    --cc=davem@davemloft.net \
    --cc=jk@codeconstruct.com.au \
    --cc=joel@jms.id.au \
    --cc=kuba@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=matt@codeconstruct.com.au \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tali.perry1@gmail.com \
    --cc=tmaimon77@gmail.com \
    --cc=venture@google.com \
    --cc=wsa@kernel.org \
    --cc=yuenn@google.com \
    --cc=zev@bewilderbeest.net \
    /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.