linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: netdev@vger.kernel.org, dave.hansen@linux.intel.com,
	linux-kernel@vger.kernel.org, goldstein.w.n@gmail.com,
	kuba@kernel.org, linuxppc-dev@lists.ozlabs.org,
	davem@davemloft.net
Subject: Re: [PATCH net-next] kunit: Fix checksum tests on big endian CPUs
Date: Fri, 25 Aug 2023 09:20:22 +0000	[thread overview]
Message-ID: <169295522241.11125.1512224356582645824.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <fe8a302c25bd0380ca030735a1383288a89adb11.1692796810.git.christophe.leroy@csgroup.eu>

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Wed, 23 Aug 2023 15:21:43 +0200 you wrote:
> On powerpc64le checksum kunit tests work:
> 
> [    2.011457][    T1]     KTAP version 1
> [    2.011662][    T1]     # Subtest: checksum
> [    2.011848][    T1]     1..3
> [    2.034710][    T1]     ok 1 test_csum_fixed_random_inputs
> [    2.079325][    T1]     ok 2 test_csum_all_carry_inputs
> [    2.127102][    T1]     ok 3 test_csum_no_carry_inputs
> [    2.127202][    T1] # checksum: pass:3 fail:0 skip:0 total:3
> [    2.127533][    T1] # Totals: pass:3 fail:0 skip:0 total:3
> [    2.127956][    T1] ok 1 checksum
> 
> [...]

Here is the summary with links:
  - [net-next] kunit: Fix checksum tests on big endian CPUs
    https://git.kernel.org/netdev/net-next/c/b38460bc463c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2023-08-25  9:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 13:21 [PATCH net-next] kunit: Fix checksum tests on big endian CPUs Christophe Leroy
2023-08-25  9: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=169295522241.11125.1512224356582645824.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=goldstein.w.n@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --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).