From: Eric Biggers <ebiggers@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH] lib/crc_kunit.c: update comment in crc_benchmark()
Date: Thu, 6 Mar 2025 09:21:51 -0800 [thread overview]
Message-ID: <20250306172151.GC1796@sol.localdomain> (raw)
In-Reply-To: <20250305015830.37813-1-ebiggers@kernel.org>
On Tue, Mar 04, 2025 at 05:58:30PM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> None of the CRC library functions use __pure anymore, so the comment in
> crc_benchmark() is outdated. But the comment was not really correct
> anyway, since the CRC computation could (in principle) be optimized out
> regardless of __pure. Update the comment to have a proper explanation.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> lib/crc_kunit.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
Applied to
https://web.git.kernel.org/pub/scm/linux/kernel/git/ebiggers/linux.git/log/?h=crc-next
- Eric
prev parent reply other threads:[~2025-03-06 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 1:58 [PATCH] lib/crc_kunit.c: update comment in crc_benchmark() Eric Biggers
2025-03-06 17:21 ` Eric Biggers [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=20250306172151.GC1796@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=ardb@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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