From: Eric Biggers <ebiggers@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Liang Kan <kan.liang@linux.intel.com>,
Yuzhuo Jing <yuzhuo@google.com>
Subject: Re: [PATCH v2 0/4] perf: Remove libcrypto dependency
Date: Wed, 25 Jun 2025 13:26:34 -0700 [thread overview]
Message-ID: <20250625202634.GE1703@sol> (raw)
In-Reply-To: <aFroVMHTBOB7wfjI@google.com>
On Tue, Jun 24, 2025 at 11:03:00AM -0700, Namhyung Kim wrote:
> Hello,
>
> On Fri, Jun 13, 2025 at 09:41:29PM -0700, Eric Biggers wrote:
> > This is a reworked version of
> > https://lore.kernel.org/all/20250521225307.743726-1-yuzhuo@google.com/.
> > I've changed it to add a new minimal SHA-1 implementation, instead of
> > trying to pull in the kernel's SHA-1 implementation which is not really
> > designed to be extracted into userspace programs. I also added a test.
> >
> > Eric Biggers (2):
> > perf build: enable -fno-strict-aliasing
> > perf util: add a basic SHA-1 implementation
> >
> > Yuzhuo Jing (2):
> > perf genelf: Remove libcrypto dependency and use built-in sha1()
> > tools: Remove libcrypto dependency
>
> Thanks for working on this. But can you please rebase it on to the
> latest perf-tools-next tree/branch? It doesn't apply cleanly.
>
> Thanks,
> Namhyung
>
Done: https://lore.kernel.org/all/20250625202311.23244-1-ebiggers@kernel.org/
- Eric
prev parent reply other threads:[~2025-06-25 20:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 4:41 [PATCH v2 0/4] perf: Remove libcrypto dependency Eric Biggers
2025-06-14 4:41 ` [PATCH v2 1/4] perf build: enable -fno-strict-aliasing Eric Biggers
2025-06-15 23:40 ` Ian Rogers
2025-06-16 1:13 ` Eric Biggers
2025-06-17 1:00 ` Ian Rogers
2025-06-14 4:41 ` [PATCH v2 2/4] perf util: add a basic SHA-1 implementation Eric Biggers
2025-06-14 4:41 ` [PATCH v2 3/4] perf genelf: Remove libcrypto dependency and use built-in sha1() Eric Biggers
2025-06-14 4:41 ` [PATCH v2 4/4] tools: Remove libcrypto dependency Eric Biggers
2025-06-24 18:03 ` [PATCH v2 0/4] perf: " Namhyung Kim
2025-06-25 20:26 ` 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=20250625202634.GE1703@sol \
--to=ebiggers@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yuzhuo@google.com \
/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).