From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bruce.ashfield@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [meta][PATCH 08/11] linux-yocto/6.18: update to v6.18.19
Date: Mon, 23 Mar 2026 22:15:27 +0000 [thread overview]
Message-ID: <b0ecbbaf6756c64d6581102e7c6fce1725c40273.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260323135057.1605923-9-bruce.ashfield@gmail.com>
On Mon, 2026-03-23 at 09:50 -0400, bruce.ashfield@gmail.com wrote:
> -SRCREV_machine ?= "d8bda5bce522d27c0e71c9190ca1d6fe4ce8c580"
> -SRCREV_meta ?= "1ee48237bcd76936b5fb21bcd3b9202faa25e18b"
> +SRCREV_machine ?= "1fa8fa91abea837d76ab91c972e8387aae78157e"
> +SRCREV_meta ?= "899d5e6d3dd929b52ec2acc5b81e317444279f19"
I'm not sure 6.18.19 was pushed to yocto-kerne-cache? 899d5e6 doesn't
seem to be there.
We're seeing missing revisions in testing:
e.g.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3492/steps/20/logs/errors
from
https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/3492
Cheers,
Richard
next prev parent reply other threads:[~2026-03-23 22:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 13:50 [PATCH 0/11] linux-yocto: consolidated pull request bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 01/11] linux-yocto/6.18: genericarm64: enable additional qcom drivers bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 02/11] linux-yocto/6.18: genericarm64: fix configuration audit warning bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 03/11] linux-yocto/6.18: update to v6.18.16 bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 04/11] linux-yocto/6.18: update CVE exclusions (6.18.16) bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 05/11] linux-yocto/6.18: update to v6.18.18 bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 06/11] linux-yocto/6.18: update CVE exclusions (6.18.18) bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 07/11] linux-yocto-dev: bump to v7.0 bruce.ashfield
2026-03-23 13:50 ` [meta][PATCH 08/11] linux-yocto/6.18: update to v6.18.19 bruce.ashfield
2026-03-23 22:15 ` Richard Purdie [this message]
2026-03-24 0:25 ` Bruce Ashfield
2026-03-23 13:50 ` [meta][PATCH 09/11] linux-yocto/6.18: update CVE exclusions (6.18.19) bruce.ashfield
2026-03-23 13:50 ` [meta-yocto-bsp][PATCH 10/11] yocto-bsps: update to v6.18.18 bruce.ashfield
2026-03-23 14:01 ` Patchtest results for " patchtest
2026-03-23 13:50 ` [meta-yocto-bsp][PATCH 11/11] yocto-bsps: update to v6.18.19 bruce.ashfield
2026-03-23 14:01 ` Patchtest results for " patchtest
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=b0ecbbaf6756c64d6581102e7c6fce1725c40273.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