public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <bruce.ashfield@gmail.com>
Cc: "Richard Purdie" <richard.purdie@linuxfoundation.org>,
	"Jan-Simon Möller" <jsmoeller@linuxfoundation.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 0/13] kernel-yocto: 6.18 updates and 6.12/6.16 removal
Date: Tue, 10 Feb 2026 16:20:10 +0100	[thread overview]
Message-ID: <DGBDT8JNFUMH.30YMHYO3TK1V7@bootlin.com> (raw)
In-Reply-To: <CADkTA4Mwt=Vq4ODNxkY=V7nJN47TM60jTAtKCrOdvAXhm1VExQ@mail.gmail.com>

On Tue Feb 10, 2026 at 3:18 PM CET, Bruce Ashfield via lists.openembedded.org wrote:
> On Tue, Feb 10, 2026 at 9:08 AM Mathieu Dubois-Briand <
> mathieu.dubois-briand@bootlin.com> wrote:
>
>> Just a note about the process while we are at it: picking this series
>> was not straightforward, at least with b4: it got confused by patches
>> 1-4 appearing twice (1 oe-core, 1 meta-yocto). It was not a big deal and
>> I have no suggestion for a better process so far, but it would be
>> helpful if patch numbers were unique.
>>
>
> My export scripts are doing that numbering on purpose, so I can definitely
> change it if it helps the picking of them.
>
> I can also just send them to the two separate lists, but I'm trying to
> simulate
> the unified series so that we don't miss coordinating between the two
> lists (and that's why the numbering is individual).
>
> I do have a "flat mode" in the tools, and that would just number them from
> 0-N through the entire series.
>
> I'm open to either option. I can send 0-N to the single list, or do the two
> 0-N sends on separate lists and let the coordination happen on your end
> between the two.
>
> Just let me know which you prefer and I'll switch to it.
>
> Bruce
>

I do not have any strong opinion here.

Having two separate 0-N series on the two separate lists is probably the
easiest one to pick on my side, but I can understand the advantage of a
single series to make sure all patches are picked in coordination. A
single series is also a working solution.

So I will let others share their opinions.

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2026-02-10 15:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 20:27 [PATCH 0/13] kernel-yocto: 6.18 updates and 6.12/6.16 removal bruce.ashfield
2026-02-06 20:27 ` [meta][PATCH 01/09] linux-yocto/6.12: update to v6.12.67 bruce.ashfield
2026-02-06 20:46   ` Patchtest results for " patchtest
2026-02-06 20:27 ` [meta][PATCH 02/09] linux-yocto/6.12: update CVE exclusions (6.12.67) bruce.ashfield
2026-02-06 20:27 ` [meta][PATCH 05/09] linux-yocto/6.18: update to v6.18.7 bruce.ashfield
2026-02-06 20:46   ` Patchtest results for " patchtest
2026-02-06 20:27 ` [meta][PATCH 06/09] linux-yocto/6.18: update CVE exclusions (6.18.7) bruce.ashfield
2026-02-06 20:27 ` [meta][PATCH 07/09] linux-yocto/6.18: beaglebone black: boot and graphics fixes bruce.ashfield
2026-02-06 20:27 ` [meta][PATCH 08/09] linux-yocto/6.18: update to v6.18.8 bruce.ashfield
2026-02-06 20:27 ` [meta][PATCH 09/09] linux-yocto/6.18: update CVE exclusions (6.18.8) bruce.ashfield
2026-02-06 20:27 ` [meta-yocto-bsp][PATCH 01/04] yocto-bsp: Bump the default kernel to v6.18 for beaglebone bruce.ashfield
2026-02-06 20:46   ` Patchtest results for " patchtest
2026-02-06 20:27 ` [meta-yocto-bsp][PATCH 02/04] meta-yocto-bsp: drop 6.12 bbappend bruce.ashfield
2026-02-06 20:46   ` Patchtest results for " patchtest
2026-02-06 20:27 ` [meta-yocto-bsp][PATCH 03/04] meta-yocto-bsp: drop 6.16 bbappend bruce.ashfield
2026-02-06 20:46   ` Patchtest results for " patchtest
2026-02-06 20:27 ` [meta-yocto-bsp][PATCH 04/04] yocto-bsp: linux-yocto/6.18: update to v6.18.8 bruce.ashfield
2026-02-06 20:46   ` Patchtest results for " patchtest
2026-02-10 10:09 ` [OE-core] [PATCH 0/13] kernel-yocto: 6.18 updates and 6.12/6.16 removal Mathieu Dubois-Briand
2026-02-10 13:19   ` Richard Purdie
2026-02-10 13:42     ` Bruce Ashfield
2026-02-10 14:08       ` Mathieu Dubois-Briand
2026-02-10 14:18         ` Bruce Ashfield
2026-02-10 15:20           ` Mathieu Dubois-Briand [this message]
2026-02-10 14:15     ` Bruce Ashfield
2026-02-10 15:10       ` 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=DGBDT8JNFUMH.30YMHYO3TK1V7@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=jsmoeller@linuxfoundation.org \
    --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