All of lore.kernel.org
 help / color / mirror / Atom feed
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, brendanhiggins@google.com,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 0/5] MCTP kunit tests
Date: Fri, 01 Oct 2021 13:20:09 +0000	[thread overview]
Message-ID: <163309440949.24017.15314464452259318665.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211001081844.3408786-1-jk@codeconstruct.com.au>

Hello:

This series was applied to netdev/net-next.git (refs/heads/master):

On Fri,  1 Oct 2021 16:18:39 +0800 you wrote:
> This change adds some initial kunit tests for the MCTP core. We'll
> expand the coverage in a future series, and augment with a few
> selftests, but this establishes a baseline set of tests for now.
> 
> Thanks to the kunit folks for the framework!
> 
> Cheers,
> 
> [...]

Here is the summary with links:
  - [net-next,1/5] mctp: Add initial test structure and fragmentation test
    https://git.kernel.org/netdev/net-next/c/8c02066b053d
  - [net-next,2/5] mctp: Add test utils
    https://git.kernel.org/netdev/net-next/c/077b6d52df6d
  - [net-next,3/5] mctp: Add packet rx tests
    https://git.kernel.org/netdev/net-next/c/925c01afb06a
  - [net-next,4/5] mctp: Add route input to socket tests
    https://git.kernel.org/netdev/net-next/c/d04dcc2d67ef
  - [net-next,5/5] mctp: Add input reassembly tests
    https://git.kernel.org/netdev/net-next/c/bbde430319ee

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-10-01 13:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01  8:18 [PATCH net-next 0/5] MCTP kunit tests Jeremy Kerr
2021-10-01  8:18 ` [PATCH net-next 1/5] mctp: Add initial test structure and fragmentation test Jeremy Kerr
2021-10-01 19:16   ` kernel test robot
2021-10-01 19:16     ` kernel test robot
2021-10-01 23:09   ` kernel test robot
2021-10-01 23:09     ` kernel test robot
2021-10-02  2:56   ` David Gow
2021-10-01  8:18 ` [PATCH net-next 2/5] mctp: Add test utils Jeremy Kerr
2021-10-01  8:18 ` [PATCH net-next 3/5] mctp: Add packet rx tests Jeremy Kerr
2021-10-02  0:39   ` kernel test robot
2021-10-02  0:39     ` kernel test robot
2021-10-01  8:18 ` [PATCH net-next 4/5] mctp: Add route input to socket tests Jeremy Kerr
2021-10-01  8:18 ` [PATCH net-next 5/5] mctp: Add input reassembly tests Jeremy Kerr
2021-10-01 13:20 ` 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=163309440949.24017.15314464452259318665.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=brendanhiggins@google.com \
    --cc=davem@davemloft.net \
    --cc=jk@codeconstruct.com.au \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.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.