From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Bruce Ashfield" <bruce.ashfield@gmail.com>
Cc: <richard.purdie@linuxfoundation.org>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [meta][PATCH 03/06] linux-yocto/7.2: update to v7.2.6
Date: Thu, 17 Sep 2026 16:37:16 +0200 [thread overview]
Message-ID: <DLHO1P7BT6HO.339WDP5TPGJBK@bootlin.com> (raw)
In-Reply-To: <CADkTA4MFxHuCVX-WNcma1Q7AzUwupf73MZTb76+W4kvZ3BQtEA@mail.gmail.com>
On Thu Sep 17, 2026 at 4:13 PM CEST, Bruce Ashfield wrote:
> On Thu, Sep 17, 2026 at 10:05 AM Antonin Godard <antonin.godard@bootlin.com>
> wrote:
>
>> Hi,
>>
>> Am I missing something or this series is missing a patch to meta-yocto-bsp
>> to
>> update SRCREV_machine:genericarm64 to 7.2.6?
>>
>
> yup. I didn't the bump, but in my rush to generate the series, I didn't
> send it out.
>
> It'll arrive shortly, I just rebased and re-generated it.
Great thanks, received :)
Antonin
next prev parent reply other threads:[~2026-09-17 14:37 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 [this message]
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 ` [PATCH 0/6] linux-yocto: cosolidated pull request Richard Purdie
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=DLHO1P7BT6HO.339WDP5TPGJBK@bootlin.com \
--to=antonin.godard@bootlin.com \
--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 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.