Openembedded Core Discussions
 help / color / mirror / Atom feed
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] [PATCH 0/7 v2] linux-yocto: consolidated pull request
Date: Wed, 2 Sep 2026 16:52:02 +0300	[thread overview]
Message-ID: <apgqAmouWiLgb40y@nuoska> (raw)
In-Reply-To: <20260902132305.3685228-1-bruce.ashfield@gmail.com>

Hi,

On Wed, Sep 02, 2026 at 09:22:57AM -0400, Bruce Ashfield via lists.openembedded.org wrote:
> meta-yocto (1):
>   linux-yocto/6.18: update to v6.18.48

Is the meta-yocto side update to v7.2 maybe missing from the series,
e.g. genericarm64?

Cheers,

-Mikko


  parent reply	other threads:[~2026-09-02 13:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02 13:22 [PATCH 0/7 v2] linux-yocto: consolidated pull request bruce.ashfield
2026-09-02 13:22 ` [meta][PATCH 01/07] linux-yocto/7.2: introduce reference kernel recipes bruce.ashfield
2026-09-02 13:22 ` [meta][PATCH 02/07] linux-yocto/7.2: BSPs: fix configuration warnings bruce.ashfield
2026-09-02 13:23 ` [meta][PATCH 03/07] linux-yocto/7.2: update to v7.2.2 bruce.ashfield
2026-09-02 13:23 ` [meta][PATCH 04/07] linux-yocto/7.2: remap rust debug info paths bruce.ashfield
2026-09-02 13:23 ` [meta][PATCH 05/07] kernel-devsrc: ship tools/include for archscripts host tools bruce.ashfield
2026-09-02 13:23 ` [meta][PATCH 06/07] linux-yocto/6.18: update to v6.18.48 bruce.ashfield
2026-09-02 13:23 ` [meta-yocto-bsp][PATCH 07/07] " bruce.ashfield
2026-09-02 13:35   ` Patchtest results for " patchtest
2026-09-02 13:52 ` Mikko Rapeli [this message]
2026-09-02 14:18   ` [OE-core] [PATCH 0/7 v2] linux-yocto: consolidated pull request 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=apgqAmouWiLgb40y@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