All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	Khem Raj <raj.khem@gmail.com>, Jon Mason <jdmason@kudzu.us>
Subject: Re: [OE-core] [PATCH 00/15] kernel-yocto: consolidated pull request
Date: Thu, 28 Apr 2022 16:43:19 -0400	[thread overview]
Message-ID: <CADkTA4Mogs+b+VxF1JfpEWVh40KSQM7HiRQ3sq1Y+s80OG4pzg@mail.gmail.com> (raw)
In-Reply-To: <16EA1387603CC89E.18966@lists.openembedded.org>

On Thu, Apr 28, 2022 at 9:48 AM Bruce Ashfield via
lists.openembedded.org
<bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
>
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> Richard,
>
> This is mainly a resend of the pull request that I sent just before
> the release builds.
>
> At that time, there was a ppc boot issue, which I've fixed. There was
> also a ptest warning, which I couldn't reproduce, so let's see if it
> pops back up on the AB.

As a follow up, I'm re-testing the ppc boot issue now. It was a
regression in the fb hotplug, which conflicted with subsequent -stable
updates. I haven't done a full series of test on PPC, so it could be
that it is undone by those updates.

Bruce

>
> There is also a known issue with some of the arm reorganization done
> for the -tiny cleaup. Jon has been working on fixes to that series, and
> I've cc'd him here so he can add context. It was some boot issues,
> even in the -standard kernel for sato (last I checked).
>
> The issue with the ARM changes is that they've already been pushed
> to my repos, so everything stacks on top. If we can't get them fixed
> shortly, I can temporarily revert and do a new patch on top.
>
> Khem has also indicated that the 5.15.36 -stable has all of the changes
> required for gcc12, so it would be a good bump to get under test.
>
> Cheers,
>
> Bruce
>
> The following changes since commit 5639708757faa00de1bc64b01220a5f7232818fb:
>
>   set_versions: update for 4.0 release (2022-04-26 10:56:47 +0100)
>
> are available in the Git repository at:
>
>   git://git.yoctoproject.org/poky-contrib zedd/kernel
>   http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
>
> Bruce Ashfield (15):
>   linux-yocto/5.15: arm: poky-tiny cleanup and fixes
>   linux-yocto/5.15: update to v5.15.33
>   linux-yocto/5.10: update to v5.10.110
>   linux-yocto/5.10: base: enable kernel crypto userspace API
>   linux-yocto/5.15: base: enable kernel crypto userspace API
>   linux-yocto/5.15: kasan: fix BUG: sleeping function called from
>     invalid context
>   kernel-yocto: allow patch author date to be commit date
>   linux-yocto/5.15: fix ppc boot
>   linux-yocto/5.15: netfilter: conntrack: avoid useless indirection
>     during conntrack destruction
>   linux-yocto/5.10: update to v5.10.112
>   linux-yocto/5.15: update to v5.15.35
>   linux-yocto/5.15: Fix CVE-2022-28796
>   linux-yocto: enable powerpc debug fragment
>   linux-yocto/5.15: fix -standard kernel build issue
>   linux-yocto/5.15: update to v5.15.36
>
>  meta/classes/kernel-yocto.bbclass             |  6 +++-
>  .../kern-tools/kern-tools-native_git.bb       |  2 +-
>  .../linux/linux-yocto-rt_5.10.bb              |  6 ++--
>  .../linux/linux-yocto-rt_5.15.bb              |  6 ++--
>  .../linux/linux-yocto-tiny_5.10.bb            |  8 +++---
>  .../linux/linux-yocto-tiny_5.15.bb            |  6 ++--
>  meta/recipes-kernel/linux/linux-yocto_5.10.bb | 26 +++++++++--------
>  meta/recipes-kernel/linux/linux-yocto_5.15.bb | 28 ++++++++++---------
>  8 files changed, 48 insertions(+), 40 deletions(-)
>
> --
> 2.19.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#164948): https://lists.openembedded.org/g/openembedded-core/message/164948
> Mute This Topic: https://lists.openembedded.org/mt/90753174/1050810
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


       reply	other threads:[~2022-04-28 20:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16EA1387603CC89E.18966@lists.openembedded.org>
2022-04-28 20:43 ` Bruce Ashfield [this message]
2022-04-28 13:47 [PATCH 00/15] kernel-yocto: consolidated pull request bruce.ashfield
2022-04-29 11:51 ` Richard Purdie
     [not found]   ` <16EA5E7263695663.11702@lists.openembedded.org>
2022-04-29 20:01     ` [OE-core] " Bruce Ashfield
     [not found]     ` <16EA76835C38B7CA.4798@lists.openembedded.org>
2022-04-30  4:26       ` Bruce Ashfield
     [not found]       ` <16EA920E59E6B6F1.28542@lists.openembedded.org>
2022-04-30 21:35         ` Bruce Ashfield
2022-05-01  4:59           ` Richard Purdie
2022-05-04  7:18             ` Nicolas Dechesne
2022-05-04 12:45               ` Bruce Ashfield
2022-05-04 14:07                 ` Jon Mason

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=CADkTA4Mogs+b+VxF1JfpEWVh40KSQM7HiRQ3sq1Y+s80OG4pzg@mail.gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=jdmason@kudzu.us \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --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.