From: patchwork-bot+netdevbpf@kernel.org
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: netdev@vger.kernel.org, matt@codeconstruct.com.au,
davem@davemloft.net, kuba@kernel.org, corbet@lwn.net,
rostedt@goodmis.org, mingo@redhat.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/5] MCTP tag control interface
Date: Wed, 09 Feb 2022 12:50:09 +0000 [thread overview]
Message-ID: <164441100999.3630.17468274065248587297.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220209040557.391197-1-jk@codeconstruct.com.au>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 9 Feb 2022 12:05:52 +0800 you wrote:
> This series implements a small interface for userspace-controlled
> message tag allocation for the MCTP protocol. Rather than leaving the
> kernel to allocate per-message tag values, userspace can explicitly
> allocate (and release) message tags through two new ioctls:
> SIOCMCTPALLOCTAG and SIOCMCTPDROPTAG.
>
> In order to do this, we first introduce some minor changes to the tag
> handling, including a couple of new tests for the route input paths.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/5] mctp: tests: Rename FL_T macro to FL_TO
https://git.kernel.org/netdev/net-next/c/62a2b005c6d6
- [net-next,v2,2/5] mctp: tests: Add key state tests
https://git.kernel.org/netdev/net-next/c/c5755214623d
- [net-next,v2,3/5] mctp: Add helper for address match checking
https://git.kernel.org/netdev/net-next/c/8069b22d656f
- [net-next,v2,4/5] mctp: Allow keys matching any local address
https://git.kernel.org/netdev/net-next/c/0de55a7d1133
- [net-next,v2,5/5] mctp: Add SIOCMCTP{ALLOC,DROP}TAG ioctls for tag control
https://git.kernel.org/netdev/net-next/c/63ed1aab3d40
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-09 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 4:05 [PATCH net-next v2 0/5] MCTP tag control interface Jeremy Kerr
2022-02-09 4:05 ` [PATCH net-next v2 1/5] mctp: tests: Rename FL_T macro to FL_TO Jeremy Kerr
2022-02-09 4:05 ` [PATCH net-next v2 2/5] mctp: tests: Add key state tests Jeremy Kerr
2022-02-09 4:05 ` [PATCH net-next v2 3/5] mctp: Add helper for address match checking Jeremy Kerr
2022-02-09 4:05 ` [PATCH net-next v2 4/5] mctp: Allow keys matching any local address Jeremy Kerr
2022-02-09 4:05 ` [PATCH net-next v2 5/5] mctp: Add SIOCMCTP{ALLOC,DROP}TAG ioctls for tag control Jeremy Kerr
2022-02-09 12:50 ` 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=164441100999.3630.17468274065248587297.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.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 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).