netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Matt Johnston <matt@codeconstruct.com.au>
Cc: netdev@vger.kernel.org, mjrinal@g.clemson.edu,
	jk@codeconstruct.com.au, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com
Subject: Re: [PATCH net 0/3] MCTP fixes
Date: Fri, 01 Apr 2022 11:10:12 +0000	[thread overview]
Message-ID: <164881141257.17879.16170877282046103440.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220401024844.1578937-1-matt@codeconstruct.com.au>

Hello:

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

On Fri,  1 Apr 2022 10:48:41 +0800 you wrote:
> Hi,
> 
> The following are fixes for the mctp core and mctp-i2c driver.
> 
> Thanks,
> Matt
> 
> [...]

Here is the summary with links:
  - [net,1/3] mctp: Fix check for dev_hard_header() result
    https://git.kernel.org/netdev/net/c/60be976ac451
  - [net,2/3] mctp i2c: correct mctp_i2c_header_create result
    https://git.kernel.org/netdev/net/c/8ce40a2fd350
  - [net,3/3] mctp: Use output netdev to allocate skb headroom
    https://git.kernel.org/netdev/net/c/4a9dda1c1da6

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



      parent reply	other threads:[~2022-04-01 11:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  2:48 [PATCH net 0/3] MCTP fixes Matt Johnston
2022-04-01  2:48 ` [PATCH net 1/3] mctp: Fix check for dev_hard_header() result Matt Johnston
2022-04-01  2:48 ` [PATCH net 2/3] mctp i2c: correct mctp_i2c_header_create result Matt Johnston
2022-04-01  2:48 ` [PATCH net 3/3] mctp: Use output netdev to allocate skb headroom Matt Johnston
2022-04-01 11: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=164881141257.17879.16170877282046103440.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jk@codeconstruct.com.au \
    --cc=kuba@kernel.org \
    --cc=matt@codeconstruct.com.au \
    --cc=mjrinal@g.clemson.edu \
    --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).