netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Coco Li <lixiaoyan@google.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH net-next 0/2] GRO and Toeplitz hash selftests
Date: Thu, 05 Aug 2021 12:30:06 +0000	[thread overview]
Message-ID: <162816660678.5517.4095732932218620845.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210805073641.3533280-1-lixiaoyan@google.com>

Hello:

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

On Thu,  5 Aug 2021 07:36:39 +0000 you wrote:
> This patch contains two selftests in net, as well as respective
> scripts to run the tests on a single machine in loopback mode.
> GRO: tests the Linux kernel GRO behavior
> Toeplitz: tests the toeplitz has implementation
> 
> Coco Li (2):
>   selftests/net: GRO coalesce test
>   selftests/net: toeplitz test
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] selftests/net: GRO coalesce test
    https://git.kernel.org/netdev/net-next/c/7d1575014a63
  - [net-next,2/2] selftests/net: toeplitz test
    https://git.kernel.org/netdev/net-next/c/5ebfb4cc3048

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-08-05 12:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05  7:36 [PATCH net-next 0/2] GRO and Toeplitz hash selftests Coco Li
2021-08-05  7:36 ` [PATCH net-next 1/2] selftests/net: GRO coalesce test Coco Li
2021-08-05 11:16   ` Paolo Abeni
2021-08-05 20:21     ` Coco Li
     [not found]     ` <CADjXwjhvb9BVNPjY2f-4yfE51RGL88U3VbiN_gwaMSGbagzQEg@mail.gmail.com>
2021-08-06  7:49       ` Paolo Abeni
2021-08-06 17:44         ` Coco Li
2021-08-05  7:36 ` [PATCH net-next 2/2] selftests/net: toeplitz test Coco Li
2021-08-05 12: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=162816660678.5517.4095732932218620845.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=lixiaoyan@google.com \
    --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).