From: "Fabio Berton" <fbberton@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [kirkstone] pseudo: Update to pull in linux-libc-headers race fix
Date: Fri, 08 Nov 2024 02:12:48 -0800 [thread overview]
Message-ID: <27448.1731060768077466772@lists.openembedded.org> (raw)
In-Reply-To: <CA+chaQcfLfXBBvnr032b3rnXwJ=mhS7zhk8zJ_h85A3dv62F9A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 85 bytes --]
Hi Martin,
Thanks for looking into this. Any action on my side?
Regards,
Fabio
[-- Attachment #2: Type: text/html, Size: 99 bytes --]
next prev parent reply other threads:[~2024-11-08 10:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 18:12 [OE-core][kirkstone] pseudo: Update to pull in linux-libc-headers race fix Fabio Berton
2024-11-06 18:15 ` Fabio Berton
2024-11-08 6:17 ` Martin Jansa
[not found] ` <1805E9CC90672053.32267@lists.openembedded.org>
2024-11-08 7:16 ` Martin Jansa
2024-11-08 10:12 ` Fabio Berton [this message]
2024-11-08 14:47 ` Steve Sakoman
2024-11-08 14:57 ` Martin Jansa
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=27448.1731060768077466772@lists.openembedded.org \
--to=fbberton@gmail.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