From: patchwork-bot+netdevbpf@kernel.org
To: Matt Johnston <matt@codeconstruct.com.au>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
jk@codeconstruct.com.au
Subject: Re: [PATCH net-next 0/3] Small fixes for MCTP
Date: Sat, 26 Feb 2022 06:30:11 +0000 [thread overview]
Message-ID: <164585701142.29742.2647756314243588093.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220225053938.643605-1-matt@codeconstruct.com.au>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 25 Feb 2022 13:39:35 +0800 you wrote:
> Hi,
>
> This series has 3 fixes for MCTP.
>
> Cheers,
> Matt
>
> [...]
Here is the summary with links:
- [net-next,1/3] mctp: Avoid warning if unregister notifies twice
https://git.kernel.org/netdev/net-next/c/f62457df5cc4
- [net-next,2/3] mctp i2c: Fix potential use-after-free
https://git.kernel.org/netdev/net-next/c/06bf1ce69d55
- [net-next,3/3] mctp i2c: Fix hard head TX bounds length check
https://git.kernel.org/netdev/net-next/c/33f5d1a9d970
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:[~2022-02-26 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 5:39 [PATCH net-next 0/3] Small fixes for MCTP Matt Johnston
2022-02-25 5:39 ` [PATCH net-next 1/3] mctp: Avoid warning if unregister notifies twice Matt Johnston
2022-02-25 5:39 ` [PATCH net-next 2/3] mctp i2c: Fix potential use-after-free Matt Johnston
2022-02-25 5:39 ` [PATCH net-next 3/3] mctp i2c: Fix hard head TX bounds length check Matt Johnston
2022-02-26 6: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=164585701142.29742.2647756314243588093.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=netdev@vger.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.