From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bruce.ashfield@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/6] linux-yocto: cosolidated pull request
Date: Thu, 17 Sep 2026 11:19:21 +0100 [thread overview]
Message-ID: <ef0bcc916d7d2f0559b6c5fd6de3373b539f01fe.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260917051340.1472139-1-bruce.ashfield@gmail.com>
Hi Bruce,
On Thu, 2026-09-17 at 01:13 -0400, bruce.ashfield@gmail.com wrote:
> Here's the pending stable updates, one of which I think I sent
> before, but I'm
> resening it to be complete.
>
> We also have a fix for the autobuilder issue. I wasn't able to
> reproduce the problem here, but this is a temporary fix until
> upstream merges something.
> It didn't break my existing use case, so let's try it on the AB.
>
> I went back to a unified patch series for this one, just to keep us
> on our toes.
Thanks for that. We can run it through a few builds but having one less
source of error noise will be good!
Cheers,
Richard
prev parent reply other threads:[~2026-09-17 10:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 5:13 [PATCH 0/6] linux-yocto: cosolidated pull request bruce.ashfield
2026-09-17 5:13 ` [meta][PATCH 01/06] linux-yocto/6.18: update to v6.18.50 bruce.ashfield
2026-09-17 5:13 ` [meta][PATCH 02/06] linux-yocto/6.18: update to v6.18.52 bruce.ashfield
2026-09-17 5:13 ` [meta][PATCH 03/06] linux-yocto/7.2: update to v7.2.6 bruce.ashfield
2026-09-17 14:05 ` [OE-core] " Antonin Godard
2026-09-17 14:13 ` Bruce Ashfield
2026-09-17 14:37 ` Antonin Godard
2026-09-17 5:13 ` [meta][PATCH 04/06] linux-yocto/7.2: drm/client: avoid spurious vblank-timeout warning bruce.ashfield
2026-09-17 5:13 ` [meta-yocto-bsp][PATCH 05/06] yocto-bsps: update to v6.18.50 bruce.ashfield
2026-09-17 5:34 ` Patchtest results for " patchtest
2026-09-17 5:13 ` [meta-yocto-bsp][PATCH 06/06] yocto-bsps: update to v6.18.52 bruce.ashfield
2026-09-17 5:34 ` Patchtest results for " patchtest
2026-09-17 10:19 ` Richard Purdie [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=ef0bcc916d7d2f0559b6c5fd6de3373b539f01fe.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@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