From: Robert Yang <liezhi.yang@windriver.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 3/3] strace: upgrade 6.19 -> 7.0
Date: Wed, 13 May 2026 16:17:36 +0800 [thread overview]
Message-ID: <ecf2526f-ff0c-4e6b-a0a5-e343cdc6ceef@windriver.com> (raw)
In-Reply-To: <1C70E210-D752-4CE0-8145-8B4FF7D58D8B@arm.com>
On 5/12/26 21:20, Ross Burton wrote:
> Hi,
>
>> On 8 May 2026, at 15:45, Robert Yang via lists.openembedded.org <liezhi.yang=windriver.com@lists.openembedded.org> wrote:
>> diff --git a/meta/recipes-connectivity/nfs-utils/nfs-utils/0001-fh_key_file.c-Fix-build-error-for-musl.patch b/meta/recipes-connectivity/nfs-utils/nfs-utils/0001-fh_key_file.c-Fix-build-error-for-musl.patch
>
> There’s nfs-utils changes in this strace upgrade, they’ll need to be put back into the right change.
Sorry, that's a mistake. I removed it and send a V2.
>
>> # remove at next version upgrade or when output changes
>> -PR = "r1"
>> HASHEQUIV_HASH_VERSION .= ".1”
>
> Remove all of this block (the comment and both assignments), not just the PR.
I removed them in V2's PULL. I didn't see this comment in the first read, sorry
about that.
// Robert
>
> Ross
>
prev parent reply other threads:[~2026-05-13 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 14:44 [PATCH 0/3] Packages upgrade liezhi.yang
2026-05-08 14:44 ` [PATCH 1/3] time: 1.9 -> 1.10 liezhi.yang
2026-05-08 14:45 ` [PATCH 2/3] nfs-utils: 2.8.7 -> 2.9.1 liezhi.yang
2026-05-08 14:45 ` [PATCH 3/3] strace: upgrade 6.19 -> 7.0 liezhi.yang
2026-05-12 13:20 ` [OE-core] " Ross Burton
2026-05-13 8:17 ` Robert Yang [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=ecf2526f-ff0c-4e6b-a0a5-e343cdc6ceef@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=Ross.Burton@arm.com \
--cc=openembedded-core@lists.openembedded.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