From: patchwork-bot+netdevbpf@kernel.org
To: Matt Johnston <matt@codeconstruct.com.au>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
jk@codeconstruct.com.au
Subject: Re: [PATCH net-next 00/10] Updates to MCTP core
Date: Wed, 29 Sep 2021 10:10:10 +0000 [thread overview]
Message-ID: <163291021014.13642.1540278409896573490.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210929072614.854015-1-matt@codeconstruct.com.au>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Wed, 29 Sep 2021 15:26:04 +0800 you wrote:
> Hi,
>
> This series adds timeouts for MCTP tags (a limited resource), and a few
> other improvements to the MCTP core.
>
> Cheers,
> Matt
>
> [...]
Here is the summary with links:
- [net-next,01/10] mctp: Allow MCTP on tun devices
https://git.kernel.org/netdev/net-next/c/f364dd71d92f
- [net-next,02/10] mctp: Allow local delivery to the null EID
https://git.kernel.org/netdev/net-next/c/1f6c77ac9e6e
- [net-next,03/10] mctp: locking, lifetime and validity changes for sk_keys
https://git.kernel.org/netdev/net-next/c/73c618456dc5
- [net-next,04/10] mctp: Add refcounts to mctp_dev
https://git.kernel.org/netdev/net-next/c/43f55f23f708
- [net-next,05/10] mctp: Implement a timeout for tags
https://git.kernel.org/netdev/net-next/c/7b14e15ae6f4
- [net-next,06/10] mctp: Add tracepoints for tag/key handling
https://git.kernel.org/netdev/net-next/c/4f9e1ba6de45
- [net-next,07/10] mctp: Do inits as a subsys_initcall
https://git.kernel.org/netdev/net-next/c/97f09abffcb9
- [net-next,08/10] doc/mctp: Add a little detail about kernel internals
https://git.kernel.org/netdev/net-next/c/f4d41c59135d
- [net-next,09/10] mctp: Set route MTU via netlink
https://git.kernel.org/netdev/net-next/c/6183569db80e
- [net-next,10/10] mctp: Warn if pointer is set for a wrong dev type
https://git.kernel.org/netdev/net-next/c/7b1871af75f3
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:[~2021-09-29 10:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 7:26 [PATCH net-next 00/10] Updates to MCTP core Matt Johnston
2021-09-29 7:26 ` [PATCH net-next 01/10] mctp: Allow MCTP on tun devices Matt Johnston
2021-09-29 7:26 ` [PATCH net-next 02/10] mctp: Allow local delivery to the null EID Matt Johnston
2021-09-29 7:26 ` [PATCH net-next 03/10] mctp: locking, lifetime and validity changes for sk_keys Matt Johnston
2021-09-29 7:26 ` [PATCH net-next 04/10] mctp: Add refcounts to mctp_dev Matt Johnston
2021-09-29 7:26 ` [PATCH net-next 05/10] mctp: Implement a timeout for tags Matt Johnston
2021-09-29 7:26 ` [PATCH net-next 06/10] mctp: Add tracepoints for tag/key handling Matt Johnston
2021-09-29 7:26 ` [PATCH net-next 07/10] mctp: Do inits as a subsys_initcall Matt Johnston
2021-09-29 7:26 ` [PATCH net-next 08/10] doc/mctp: Add a little detail about kernel internals Matt Johnston
2021-09-29 7:26 ` [PATCH net-next 09/10] mctp: Set route MTU via netlink Matt Johnston
2021-09-29 7:26 ` [PATCH net-next 10/10] mctp: Warn if pointer is set for a wrong dev type Matt Johnston
2021-09-29 10: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=163291021014.13642.1540278409896573490.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 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).