All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] kernel-yocto: consolidated pull request
Date: Mon,  3 Aug 2020 08:30:24 -0400	[thread overview]
Message-ID: <cover.1596457310.git.bruce.ashfield@gmail.com> (raw)

From: Bruce Ashfield <bruce.ashfield@gmail.com>

Hi all,

This series contains two routine updates of 5.4. The -stable update and
a backport to fix a perf build issue with the new binutils (as reported
and debugged by Khem).

The other two are features that I've been working on for the fall release.
One is minor (the dangling kernel_features warning) and one is a
significant re-write of the kernel configuration auditing tools and has
been taking place over the past three weeks.

The dangling features change is just to allow more flexibility with
layers and the types of features they may be requesting. The details
are in the commit log. By default the behaviour is the same, so there
shouldn't be any issues (since if a feature is missing, someone's
build was already stopping).

The configuration queue one is an update of the symbol analysis to
include looking at the fragments to provide details when the common
question is asked "why didn't my config value make it into the .config".
We now get detailed forensics from within the kernel configuration
system (to deal with issues when something is selected, or not visible)
and also insight into what fragment(s) set values. The tweaks are run
both as part of the standard kernel-yocto build and through a dedicated
task for deugging.

I expect that the configuration update may trigger some warnings, since
it finds things that the old tools couldn't. As such, if it causes
any issues, just drop it from the queue and take the other patches. I
wasn't able to run all the builds for it, but did get through multiple
green builds on the AB and locally .. so this needs to get some wider
testing now.

Cheers,

Bruce


The following changes since commit 20e9df57217c5f37817653d2c3d492f2d4d37623:

  lib/oe/reproducible.py: Fix git HEAD check (2020-07-29 11:37:31 +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 (4):
  linux-yocto/5.4: update to v5.4.53
  linux-yocto/5.4: fix perf build with binutils 2.35
  kernel/yocto: allow dangling KERNEL_FEATURES
  kernel-yocto: enhance configuration queue analysis capabilities

 meta/classes/kernel-yocto.bbclass             | 191 ++++++++++++++----
 .../kern-tools/kern-tools-native_git.bb       |   2 +-
 .../linux/linux-yocto-rt_5.4.bb               |   6 +-
 .../linux/linux-yocto-tiny_5.4.bb             |   8 +-
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  |  24 +--
 5 files changed, 175 insertions(+), 56 deletions(-)

-- 
2.19.1


             reply	other threads:[~2020-08-03 12:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 12:30 Bruce Ashfield [this message]
2020-08-03 12:30 ` [PATCH 1/4] linux-yocto/5.4: update to v5.4.53 Bruce Ashfield
2020-08-03 12:30 ` [PATCH 2/4] linux-yocto/5.4: fix perf build with binutils 2.35 Bruce Ashfield
2020-08-03 12:30 ` [PATCH 3/4] kernel/yocto: allow dangling KERNEL_FEATURES Bruce Ashfield
2020-08-03 12:30 ` [PATCH 4/4] kernel-yocto: enhance configuration queue analysis capabilities Bruce Ashfield
  -- strict thread matches above, loose matches on Subject: below --
2025-04-10 18:55 [PATCH 0/4] kernel-yocto: consolidated pull request bruce.ashfield
2025-04-10 20:24 ` Richard Purdie
2020-03-04 14:55 bruce.ashfield
2020-03-04 14:56 ` Bruce Ashfield
2020-03-04 14:57 ` Bruce Ashfield
2019-12-30  3:07 bruce.ashfield
2016-12-02 21:09 Bruce Ashfield
2016-12-06 19:32 ` Trevor Woerner
2015-03-02 21:36 Bruce Ashfield
2013-05-31  3:28 Bruce Ashfield
2013-05-31  6:14 ` Saul Wold
2013-05-31  7:07   ` Richard Purdie
2013-05-31 12:29     ` 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=cover.1596457310.git.bruce.ashfield@gmail.com \
    --to=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 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.