From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
Andrei Gherzan <andrei@gherzan.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/9] kernel-yocto: consolidated pull request
Date: Tue, 20 Sep 2022 13:55:26 +0100 [thread overview]
Message-ID: <aa9014096363f371afa9b472ea8fce3329d80eaa.camel@linuxfoundation.org> (raw)
In-Reply-To: <CADkTA4Oon-WbV8x+TTfhDH2eGo6yjoQpxPsE-RXuqU0u7OWx0g@mail.gmail.com>
On Tue, 2022-09-20 at 08:53 -0400, Bruce Ashfield wrote:
> On Tue, Sep 20, 2022 at 8:22 AM Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >
> > On Mon, 2022-09-19 at 10:28 -0400, bruce.ashfield@gmail.com wrote:
> > > From: Bruce Ashfield <bruce.ashfield@gmail.com>
> > >
> > > Richard,
> > >
> > > Here's the next set of -stable updates to the active reference kernels.
> > > I also have updates back to 5.4 that I'll send to the various stable
> > > branches shortly.
> > >
> > > I also have a couple of kern-tools fixes. One to solve a problem reported
> > > on the list about some directory structures (typically created from KAS)
> > > to break the meta-data phase of the kernel build. I've fixed that issue,
> > > then fixed the other regressions that fix caused, and have everything
> > > passing sanity. There shouldn't be any fallout, but I'll be keeping a
> > > close eye on things.
> > >
> > > I also have Khem's MDIO configuration change in the queue, along with
> > > a previously hidden kern-tools feature that allows it to not warn if
> > > something is 'enabled' (y or m).
> >
> > I have a patch in master-next I'm testing for the perf issue. On
> > testing that, this set of config warnings became clear for poky-tiny:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157
>
> That's very likely due to this change from Andrei :
> https://git.yoctoproject.org/yocto-kernel-cache/commit/?h=yocto-5.19&id=d334505d98a85ffe7549026d10e43cccd897e19c
>
> Was that a qemuarm64 configuration ?
It warned on qemux86:
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/12/logs/stdio
qemux86-64:
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/16/logs/stdio
qemuarm64:
https://autobuilder.yoctoproject.org/typhoon/#/builders/15/builds/6157/steps/18/logs/stdio
so on all the arches we test for tiny.
Cheers,
Richard
next prev parent reply other threads:[~2022-09-20 12:55 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 14:28 [PATCH 0/9] kernel-yocto: consolidated pull request bruce.ashfield
2022-09-19 14:28 ` [PATCH 1/9] linux-yocto/5.15: update to v5.15.63 bruce.ashfield
2022-09-19 14:28 ` [PATCH 2/9] linux-yocto/5.19: update to v5.19.5 bruce.ashfield
2022-09-19 14:28 ` [PATCH 3/9] linux-yocto/5.19: update to v5.19.7 bruce.ashfield
2022-09-19 14:28 ` [PATCH 4/9] linux-yocto/5.15: update to v5.15.65 bruce.ashfield
2022-09-19 14:28 ` [PATCH 5/9] kern-tools: fix queue processing in relative TOPDIR configurations bruce.ashfield
2022-09-19 14:28 ` [PATCH 6/9] linux-yocto: Enable mdio for qemu bruce.ashfield
2022-09-19 14:28 ` [PATCH 7/9] kern-tools: allow 'y' or 'm' to avoid config audit warnings bruce.ashfield
2022-09-19 14:28 ` [PATCH 8/9] linux-yocto/5.19: update to v5.19.9 bruce.ashfield
2022-09-19 14:28 ` [PATCH 9/9] linux-yocto/5.15: update to v5.15.68 bruce.ashfield
2022-09-23 21:31 ` [OE-core] " Steve Sakoman
2022-09-24 2:21 ` Bruce Ashfield
2022-09-24 2:32 ` Steve Sakoman
2022-09-19 21:23 ` [OE-core] [PATCH 0/9] kernel-yocto: consolidated pull request Khem Raj
2022-09-20 9:45 ` Richard Purdie
2022-09-20 12:21 ` Richard Purdie
2022-09-20 12:53 ` Bruce Ashfield
2022-09-20 12:55 ` Richard Purdie [this message]
2022-09-20 20:29 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2021-05-17 22:16 Bruce Ashfield
2020-02-05 23:12 bruce.ashfield
2020-02-06 9:03 ` Richard Purdie
2020-02-06 13:25 ` Bruce Ashfield
2018-06-07 2:07 Bruce Ashfield
2018-03-06 18:11 Bruce Ashfield
2017-09-14 13:46 Bruce Ashfield
2017-08-21 2:58 Bruce Ashfield
2017-08-21 11:42 ` Richard Purdie
2017-08-21 12:11 ` Bruce Ashfield
2017-08-21 13:01 ` Bruce Ashfield
2017-08-21 15:55 ` Richard Purdie
2017-08-21 15:57 ` Bruce Ashfield
2017-08-21 16:12 ` Bruce Ashfield
2017-08-22 14:24 ` Richard Purdie
2017-08-22 14:54 ` Bruce Ashfield
2017-08-22 15:28 ` Richard Purdie
2017-08-22 15:34 ` Bruce Ashfield
2017-08-22 16:00 ` Richard Purdie
2017-08-22 16:04 ` Bruce Ashfield
2017-08-22 16:07 ` Richard Purdie
2017-08-22 16:20 ` Bruce Ashfield
2017-08-22 17:13 ` Bruce Ashfield
2017-08-22 20:34 ` Bruce Ashfield
2017-08-22 21:56 ` 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=aa9014096363f371afa9b472ea8fce3329d80eaa.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=andrei@gherzan.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox