public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Yuzhuo Jing <yuzhuo@google.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	 Ian Rogers <irogers@google.com>,
	linux-crypto@vger.kernel.org,  linux-kernel@vger.kernel.org
Cc: Yuzhuo Jing <yuzhuo@google.com>
Subject: [PATCH v1 0/2] crypto: Fix sha1 compile error
Date: Fri, 13 Jun 2025 17:08:26 -0700	[thread overview]
Message-ID: <20250614000828.311722-1-yuzhuo@google.com> (raw)

This is a followup patch series for an ongoing patch series to reuse
kernel tree sha1 utils in perf tools and remove libcrypto dependency.
This mirrors the fixes made in perf back to the kernel tree so we can
use tools/perf/check-headers.sh to monitor future changes.
Link: https://lore.kernel.org/lkml/aC9lXhPFcs5fkHWH@x1/t/#u

This series contains two patches: one fixing signed and unsigned integer
comparisons and another fixing function type mismatches.

Yuzhuo Jing (2):
  crypto: Fix sha1 signed integer comparison compile error
  crypto: Fix sha1 signed pointer comparison compile error

 crypto/sha1_generic.c      | 2 +-
 include/crypto/sha1_base.h | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

-- 
2.50.0.rc1.591.g9c95f17f64-goog


             reply	other threads:[~2025-06-14  0:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-14  0:08 Yuzhuo Jing [this message]
2025-06-14  0:08 ` [PATCH v1 1/2] crypto: Fix sha1 signed integer comparison compile error Yuzhuo Jing
2025-06-14  0:08 ` [PATCH v1 2/2] crypto: Fix sha1 signed pointer " Yuzhuo Jing
2025-06-14  4:53 ` [PATCH v1 0/2] crypto: Fix sha1 " Eric Biggers

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=20250614000828.311722-1-yuzhuo@google.com \
    --to=yuzhuo@google.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=irogers@google.com \
    --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