From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: bruce.ashfield@gmail.com
Cc: richard.purdie@linuxfoundation.org,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [meta][PATCH 01/02] linux-yocto/6.18: update to v6.18.50
Date: Wed, 16 Sep 2026 09:34:45 +0300 [thread overview]
Message-ID: <aqo4hfLnicviWL3O@nuoska> (raw)
In-Reply-To: <CADkTA4PK+tZuCHuBR4ZPahYUYy4QmYEoz85Vv1q34AT70c8mMg@mail.gmail.com>
Hi Bruce,
On Tue, Sep 15, 2026 at 05:50:36PM -0400, Bruce Ashfield via lists.openembedded.org wrote:
> There's no second patch coming, it went to the yocto list for BSPs!
I don't see the yocto-bsp side patch in https://lists.yoctoproject.org/g/poky/messages list
archives. Same was with previous kernel update series.
Maybe they just went to Richard directly?
Cheers,
-Mikko
next prev parent reply other threads:[~2026-09-16 6:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18D59CE1160E5503.1924412@lists.openembedded.org>
2026-09-15 21:50 ` [OE-core] [meta][PATCH 01/02] linux-yocto/6.18: update to v6.18.50 Bruce Ashfield
2026-09-16 6:34 ` Mikko Rapeli [this message]
2026-09-16 7:16 ` Antonin Godard
2026-09-16 7:29 ` Mikko Rapeli
2026-09-16 14:22 ` Bruce Ashfield
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=aqo4hfLnicviWL3O@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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