Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Bruce Ashfield" <bruce.ashfield@gmail.com>
Cc: richard.purdie@linuxfoundation.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 00/10] linux-yocto: consolidated pull request
Date: Tue, 22 Aug 2023 09:13:44 +0200	[thread overview]
Message-ID: <20230822091344.2301ed50@booty> (raw)
In-Reply-To: <cover.1692632563.git.bruce.ashfield@gmail.com>

Hello Bruce,

On Mon, 21 Aug 2023 11:44:35 -0400
"Bruce Ashfield" <bruce.ashfield@gmail.com> wrote:

> From: Bruce Ashfield <bruce.ashfield@gmail.com>
> 
> Richard,
> 
> While we track down the remaining 6.4 boot issues, here is the
> set of -stable and specific fixes that I've queued in my kernel
> testing tree.
> 
> It is possible that some of the 6.4-stable's have fixes for our
> boot issues, but I didn't see anything obvious.
> 
> In particular we have the -rt warning fix from PaulG and also
> a fixup on our isocpus patch.
> 
> Cheers,
> 
> Bruce

You're probably already aware of the build failure triggered by this
patch series:

  stdio: ERROR: linux-yocto-6.4.11+gitAUTOINC+d9483a24c9_9753b44979-r0 do_fetch: Fetcher failure: Unable to find revision d9483a24c9ee33b6e566baa5233cbd9feaeb5212 in branch yocto-6.4 even from upstream

This one is less visible:

  WARNING: linux-yocto-6.4.11+gitAUTOINC+d9483a24c9_9753b44979-r0 do_kernel_configcheck: [kernel config]: This BSP contains fragments with warnings:

  [INFO]: the following symbols were not found in the active configuration:
       - CONFIG_COMMON_CLK_NPCM8XX

https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/4440/steps/17/logs/stdio

Luca

-- 
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  parent reply	other threads:[~2023-08-22  7:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21 15:44 [PATCH 00/10] linux-yocto: consolidated pull request bruce.ashfield
2023-08-21 15:44 ` [PATCH 01/10] linux-yocto/6.1: update to v6.1.44 bruce.ashfield
2023-08-21 15:44 ` [PATCH 02/10] linux-yocto/6.4: update to v6.4.10 bruce.ashfield
2023-08-21 15:44 ` [PATCH 03/10] linux-yocto/6.1: update to v6.1.45 bruce.ashfield
2023-08-21 15:44 ` [PATCH 04/10] kern-tools: include utility to post process config diffs bruce.ashfield
2023-08-21 15:44 ` [PATCH 05/10] linux-yocto/6.1: fix uninitialized read in nohz_full/isolcpus setup bruce.ashfield
2023-08-21 15:44 ` [PATCH 06/10] linux-yocto/6.4: " bruce.ashfield
2023-08-21 15:44 ` [PATCH 07/10] linux-yocto/6.4: update to v6.4.11 bruce.ashfield
2023-08-21 15:44 ` [PATCH 08/10] linux-yocto/6.1: update to v6.1.46 bruce.ashfield
2023-08-21 15:44 ` [PATCH 09/10] linux-yocto/6.1: fix IRQ-80 warnings bruce.ashfield
2023-08-21 15:44 ` [PATCH 10/10] linux-yocto/6.4: " bruce.ashfield
2023-08-21 15:47 ` [PATCH 00/10] linux-yocto: consolidated pull request Richard Purdie
2023-08-21 15:50   ` Bruce Ashfield
2023-08-22  7:13 ` Luca Ceresoli [this message]
2023-08-22  7:44   ` [OE-core] " Mikko Rapeli
2023-08-22 12:47   ` 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=20230822091344.2301ed50@booty \
    --to=luca.ceresoli@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