From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: James Clark <james.clark@linaro.org>
Cc: sashiko-reviews@lists.linux.dev, dmitry.torokhov@gmail.com,
linux-perf-users@vger.kernel.org, bpf@vger.kernel.org,
linux-input@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH v2 5/6] tools/build: selftests: Allow versioning LLVM lld
Date: Fri, 10 Jul 2026 15:26:51 -0700 [thread overview]
Message-ID: <a0aeb1e7-5c12-4211-be17-6ae94ef0e04e@linux.dev> (raw)
In-Reply-To: <e060c4cf-59fe-42f0-bb05-adb520a6c80a@linaro.org>
On 5/21/26 6:16 AM, James Clark wrote:
>
>
> On 20/05/2026 8:50 pm, Arnaldo Carvalho de Melo wrote:
>> On Mon, May 18, 2026 at 10:47:53AM +0100, James Clark wrote:
>>>
>>> [...]
>>
>> Hey, this touches several tools and libs, did you get acks besides the
>> one from Ian?
>>
>> - Arnaldo
>
> Only the build bpf failure report from Ihor on V1 but nothing from anyone on V2. Ihor did you get a chance to look at this version?
Hi James. I'm terribly sorry for long delay, I missed your ping.
The first thing to note is that the series doesn't apply anymore to
either bpf-next or 7.2-rc2, so please respin when you get a chance.
Other than that I have two comments.
Will reply to the patches shortly.
>
> Thanks
> James
>
next prev parent reply other threads:[~2026-07-10 22:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 9:03 [PATCH v2 0/6] tools/build: Allow versioning of all LLVM tools James Clark
2026-05-18 9:03 ` [PATCH v2 1/6] tools/build: Allow versioning of all LLVM tools defined in Makefile.include James Clark
2026-05-18 9:03 ` [PATCH v2 2/6] tools/build: Indent if else blocks James Clark
2026-05-18 9:03 ` [PATCH v2 3/6] selftests: Remove unused LLD variable James Clark
2026-05-21 15:30 ` Benjamin Tissoires
2026-05-18 9:03 ` [PATCH v2 4/6] tools/build: Allow versioning LLVM readelf James Clark
2026-05-18 16:05 ` Ian Rogers
2026-07-10 22:29 ` Ihor Solodrai
2026-05-18 9:03 ` [PATCH v2 5/6] tools/build: selftests: Allow versioning LLVM lld James Clark
2026-05-18 9:32 ` sashiko-bot
2026-05-18 9:47 ` James Clark
2026-05-20 19:50 ` Arnaldo Carvalho de Melo
2026-05-21 13:16 ` James Clark
2026-07-10 22:26 ` Ihor Solodrai [this message]
2026-07-10 22:30 ` Ihor Solodrai
2026-05-18 9:03 ` [PATCH v2 6/6] tools/build: selftests: Remove some duplicate toolchain definitions James Clark
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=a0aeb1e7-5c12-4211-be17-6ae94ef0e04e@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=acme@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=james.clark@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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