From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bruce.ashfield@gmail.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 0/2] kernel-yocto: drop 5.19 recipes and make 6.1 default
Date: Thu, 26 Jan 2023 17:21:43 +0100 [thread overview]
Message-ID: <Y9Kol1jla2OQMzOa@mail.local> (raw)
In-Reply-To: <030b78056586e38cbaca26055da1af61a9786e0d.camel@linuxfoundation.org>
On 26/01/2023 12:39:02+0000, Richard Purdie wrote:
> On Tue, 2023-01-24 at 16:59 -0500, bruce.ashfield@gmail.com wrote:
> > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> >
> > Richard,
> >
> > As promised, here are the commits to switch us over to 6.1 as the
> > default.
> >
> > I'll also send a series for poky to bump things there as well.
> >
> > Also, if there are any significant problems, we'll just shelve this
> > while I look at any issues. But at this point, it is worth getting
> > the patches out there to move the needle to 6.1
>
> Thanks!
>
> I think the issues are:
>
> a) two selftest failures:
>
> oe-selftest -r devtool.DevtoolUpgradeTests.test_devtool_virtual_kernel_modify
> oe-selftest -r efibootpartition.GenericEFITest.test_boot_efi
>
> b) meta-arm issues
>
> c) meta-virt issue (which you have a patch pending for in -next)
>
Unfortunately, I have to add
d) perf reproducibility issues:
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2294/steps/13/logs/stdio
> I suspect we can switch poky-tiny and defer the removal patches for a
> few days to give meta-arm time to sort itself out. The only question
> then becomes the selftest issues. I'm taking a quick look to see if
> they're simple to sort.
>
> Cheers,
>
> Richard
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#176392): https://lists.openembedded.org/g/openembedded-core/message/176392
> Mute This Topic: https://lists.openembedded.org/mt/96508797/3617179
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alexandre.belloni@bootlin.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-01-26 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 21:59 [PATCH 0/2] kernel-yocto: drop 5.19 recipes and make 6.1 default bruce.ashfield
2023-01-24 21:59 ` [PATCH 1/2] linux-yocto/5.19: drop recipes bruce.ashfield
2023-01-24 21:59 ` [PATCH 2/2] conf/qemu: bump preferred kernel version to 6.1 bruce.ashfield
2023-01-26 12:39 ` [PATCH 0/2] kernel-yocto: drop 5.19 recipes and make 6.1 default Richard Purdie
2023-01-26 16:21 ` Alexandre Belloni [this message]
2023-01-26 16:36 ` [OE-core] " Richard Purdie
2023-01-26 16:57 ` Bruce Ashfield
2023-01-26 17:07 ` Bruce Ashfield
2023-01-26 17:34 ` Richard Purdie
2023-01-26 17:58 ` Khem Raj
2023-01-26 18:06 ` Bruce Ashfield
2023-01-26 18:20 ` Khem Raj
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=Y9Kol1jla2OQMzOa@mail.local \
--to=alexandre.belloni@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox