From: Sam James <sam@gentoo.org>
To: Eugene Loh <eugene.loh@oracle.com>
Cc: dtrace@lists.linux.dev
Subject: Re: [PATCH 4/4] test: allow overriding CC, OBJCOPY, OBJDUMP, NM, ...
Date: Sat, 10 May 2025 02:50:37 +0100 [thread overview]
Message-ID: <87o6w1w7wy.fsf@gentoo.org> (raw)
In-Reply-To: <f5e23dde-b868-5142-5487-7a34aef7e796@oracle.com>
Eugene Loh <eugene.loh@oracle.com> writes:
> I went ahead and rebased the patch on origin/dev, incorporated my
> suggestions, and ran the test suite to check things out. I'll post a
> v2 of the patch momentarily. I hope that's okay. I don't mean to
> step on your toes, but the patch has so many little changes that it'd
> be nice to get these changes made and then adhere to the new practice.
Please do -- and thank you!
>
> On 2/25/25 19:09, Sam James wrote:
>> Eugene Loh <eugene.loh@oracle.com> writes:
>>
>>> I'm open to signing off on this patch, but I have some questions:
>> Thanks for the reviews. I'm just replying to let you know it may be a
>> little while before I can handle answering & respinning.
>>
>>> [...]
>> sam
>>
prev parent reply other threads:[~2025-05-10 1:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 2:49 [PATCH 0/4] Further test cleanups Sam James
2025-01-24 2:49 ` [PATCH 1/4] test: fix 'harness' typo Sam James
2025-02-25 18:28 ` Eugene Loh
2025-01-24 2:49 ` [PATCH 2/4] test: fix bashism in tst.bitfield-offset.x Sam James
2025-02-25 21:29 ` Eugene Loh
2025-01-24 2:49 ` [PATCH 3/4] test: finalize porting small awk stragglers to gawk Sam James
2025-02-25 21:39 ` Eugene Loh
2025-01-24 2:49 ` [PATCH 4/4] test: allow overriding CC, OBJCOPY, OBJDUMP, NM, Sam James
2025-02-25 22:26 ` Eugene Loh
2025-02-26 0:09 ` Sam James
2025-05-09 4:59 ` Eugene Loh
2025-05-10 1:50 ` Sam James [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=87o6w1w7wy.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=dtrace@lists.linux.dev \
--cc=eugene.loh@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.