From: Michael Ellerman <mpe@ellerman.id.au>
To: Palmer Dabbelt <palmer@dabbelt.com>,
Charlie Jenkins <charlie@rivosinc.com>
Cc: linux@roeck-us.net, David.Laight@aculab.com,
akpm@linux-foundation.org, deller@gmx.de,
James.Bottomley@hansenpartnership.com,
linux-parisc@vger.kernel.org, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org,
Charlie Jenkins <charlie@rivosinc.com>,
lkp@intel.com
Subject: Re: [PATCH v9 0/2] lib: checksum: Fix issues with checksum tests
Date: Fri, 23 Feb 2024 18:22:30 +1100 [thread overview]
Message-ID: <87plwnabm1.fsf@mail.lhotse> (raw)
In-Reply-To: <mhng-7bd71679-7e7b-459d-8d6f-068a0ee090ba@palmer-ri-x1c9a>
Palmer Dabbelt <palmer@dabbelt.com> writes:
> On Wed, 21 Feb 2024 18:55:48 PST (-0800), Charlie Jenkins wrote:
>> The ip_fast_csum and csum_ipv6_magic tests did not work on all
>> architectures due to differences in endianness and misaligned access
>> support. Fix those issues by changing endianness of data and aligning
>> the data.
>>
>> Signed-off-by: Charlie Jenkins <charlie@rivosinc.com>
>> ---
>> Changes in v9:
>> - Revert back to v7, the changes to v8 were not needed
>> - Link to v8: https://lore.kernel.org/r/20240214-fix_sparse_errors_checksum_tests-v8-0-36b60e673593@rivosinc.com
...
>>
>> ---
>> Charlie Jenkins (2):
>> lib: checksum: Fix type casting in checksum kunits
>> lib: checksum: Use aligned accesses for ip_fast_csum and csum_ipv6_magic tests
>>
>> lib/checksum_kunit.c | 396 ++++++++++++++++++---------------------------------
>> 1 file changed, 136 insertions(+), 260 deletions(-)
>> ---
>> base-commit: 6613476e225e090cc9aad49be7fa504e290dd33d
>> change-id: 20240119-fix_sparse_errors_checksum_tests-26b86b34d784
>
> I put a
>
> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
>
> on the v4, but looks like it got lost. I'm happy to take this via the
> RISC-V tree, as that's how I merged the broken patches in the first
> place, but no big deal if someone else wants to pick it up.
>
> It looks like the issues are all resolved and such, but there's been a
> long tail of them so I'm not 100% sure here...
I tested v9 on ppc32/64 BE, and it fixes the test failures and the
sparse errors, so LGTM.
Tested-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)
cheers
next prev parent reply other threads:[~2024-02-23 7:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 2:55 [PATCH v9 0/2] lib: checksum: Fix issues with checksum tests Charlie Jenkins
2024-02-22 2:55 ` [PATCH v9 1/2] lib: checksum: Fix type casting in checksum kunits Charlie Jenkins
2024-02-23 9:13 ` Christophe Leroy
2024-02-22 2:55 ` [PATCH v9 2/2] lib: checksum: Use aligned accesses for ip_fast_csum and csum_ipv6_magic tests Charlie Jenkins
2024-02-23 10:06 ` Christophe Leroy
2024-02-23 10:28 ` David Laight
2024-02-23 14:49 ` Guenter Roeck
2024-02-23 17:54 ` Charlie Jenkins
2024-02-22 20:27 ` [PATCH v9 0/2] lib: checksum: Fix issues with checksum tests Palmer Dabbelt
2024-02-23 7:22 ` Michael Ellerman [this message]
2024-02-23 9:22 ` Christophe Leroy
2024-02-23 17:39 ` Charlie Jenkins
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=87plwnabm1.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=David.Laight@aculab.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=charlie@rivosinc.com \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkp@intel.com \
--cc=palmer@dabbelt.com \
--cc=viro@zeniv.linux.org.uk \
/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).