All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bruce.ashfield@gmail.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] kernel-yocto: consolidated pull request
Date: Sat, 08 Aug 2026 08:52:21 +0100	[thread overview]
Message-ID: <aee8e7be6036b51dd95fa5bff923322765d6dc66.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260807162900.2623274-1-bruce.ashfield@gmail.com>

Hi Bruce,

On Fri, 2026-08-07 at 12:28 -0400, bruce.ashfield@gmail.com wrote:
> Here are the latest linux-yocto bumps for both the core and
> reference BSPs.
> 
> Note: v7.2 will be the next reference kernel, it is on rc6 now,
> so expect both that an a libc-headers bump in the next few
> weeks.

I can see the 6.18.41 revisions in:

https://git.yoctoproject.org/linux-yocto/log/?h=v6.18/standard/base

but I can't see 6.18.43 there. The builds are failing with:

ERROR: linux-yocto-6.18.43+git-r0 do_fetch: Fetcher failure: Unable to find revision 73fd4709c133ba2ee6012cfb6a63eb908d1a5cc6 in branch v6.18/standard/base even from upstream
ERROR: linux-yocto-6.18.43+git-r0 do_fetch: Bitbake Fetcher Error: FetchError('Unable to fetch URL from any source.', 'git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=v6.18/standard/base;protocol=https')

which is probably a result of that. Maybe a failed push?

Cheers,

Richard


  parent reply	other threads:[~2026-08-08  7:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07 16:28 [PATCH 0/4] kernel-yocto: consolidated pull request bruce.ashfield
2026-08-07 16:28 ` [meta][PATCH 01/04] linux-yocto/6.18: update to v6.18.41 bruce.ashfield
2026-08-07 16:28 ` [meta][PATCH 02/04] linux-yocto/6.18: update to v6.18.43 bruce.ashfield
2026-08-07 16:28 ` [meta-yocto-bsp][PATCH 03/04] yocto-bsps: update to v6.18.41 bruce.ashfield
2026-08-07 16:48   ` Patchtest results for " patchtest
2026-08-07 16:28 ` [meta-yocto-bsp][PATCH 04/04] yocto-bsps: update to v6.18.43 bruce.ashfield
2026-08-07 16:48   ` Patchtest results for " patchtest
2026-08-08  7:52 ` Richard Purdie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-10 18:55 [PATCH 0/4] kernel-yocto: consolidated pull request bruce.ashfield
2025-04-10 20:24 ` Richard Purdie
2020-08-03 12:30 Bruce Ashfield
2020-03-04 14:55 bruce.ashfield
2020-03-04 14:56 ` Bruce Ashfield
2020-03-04 14:57 ` Bruce Ashfield
2019-12-30  3:07 bruce.ashfield
2016-12-02 21:09 Bruce Ashfield
2016-12-06 19:32 ` Trevor Woerner
2015-03-02 21:36 Bruce Ashfield
2013-05-31  3:28 Bruce Ashfield
2013-05-31  6:14 ` Saul Wold
2013-05-31  7:07   ` Richard Purdie
2013-05-31 12:29     ` 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=aee8e7be6036b51dd95fa5bff923322765d6dc66.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.