[PATCH 0/5] kernel-yocto: consolidated pull request

[PATCH 0/5] kernel-yocto: consolidated pull request

[Bruce Ashfield]

Richard/Saul,

This pull request is a collection of bug fixes and feature additions
for the 1.4 release. Documentation updates are underway for the new
features, but they've soaked long enough here, so I wanted to get
them out while there's lots of time to address any issues.

[PATCH 1/5] guilt: remove GIT_EXEC_BASE export

  This fixes a bug that has been reported off and on for nearly a 
  year now. I finally saw it on my local machine and was able to
  track down the cause .. and export of GIT_EXEC_BASE that is no
  longer needed. Although I may get rid of guilt shortly, it's still
  worth fixing this now.

[PATCH 2/5] kernel-yocto: make configuration audit details debug only

  This addresses [YOCTO #3415], and simply makes the full kernel
  configuration audit slightly less visible, but yet still available.

[PATCH 3/5] kernel-yocto: fix .scc and .cfg matching

  I ran into this while implementing a new feature, some local 
  SRC_URIs were matching fragments incorrectly. With this fix
  I'm back to only getting .scc and .cfg files.

[PATCH 4/5] kernel-yocto: allow multiple / shared kernel feature directories

  This is the most interesting addition of this series, and it's
  the start of solving the problem of having multiple people developing
  disjoint sets of kernel configuration blocks, or kernel features. 

  To promote the reuse and sharing of configuration fragments this change
  allows any kernel-yocto based recipe to have multiple alternate git repositories
  which provide kernel feature directory trees listed on the SRC_URI.

  These feature directories are in addition to any in-tree kernel meta data branches
  that may be available (described via the KMETA variable in linux-yocto recipes).

  Features found within these directories can be used from recipes via the
  KERNEL_FEATURES variable. Features found within a feature directory are free
  to include any other features that are available in any directories. In both
  cases the path to a feature description (a .scc file) is relative to the
  root of a given feature directory (which is how existing .scc files work)

  The search order for features is determined by the order that repositories
  appear on the SRC_URI.

  Normal SRC_URI rules apply to any repository that is added as a kernel
  feature container. A SRCREV must be supplied and it must be unpacked to
  a unique directory, which is controlled via the "destsuffic" url parameter.

  In addition to these standard requirements, any kernel feature repository
  reference should identify itself via the "type=kmeta" url parameter. If
  type=kmeta is not supplied, the repository will not be processed for
  kernel features.

  As an example, the following in a linux-yocto bbappend makes two additional
  feature directories available to KERNEL_FEATURES and fragments.

    SRC_URI += "git://git.yoctoproject.org/yocto-kernel-cache;protocol=git;branch=master;type=kmeta;name=feat1;destsuffix=kernel-cache/"
    SRC_URI += "git://${KSRC_linux_yocto_3_4};protocol=file;branch=meta;name=feat2;type=kmeta;destsuffix=kernel-features-experimental/"

    SRCREV_feat1 = "${AUTOREV}"
    SRCREV_feat2 = "${AUTOREV}"

[PATCH 5/5] kernel-yocto/linux-yocto-custom: support low bandwidth options

  To support configurations where active development is not being done within
  the oe/bitbake build environment and restricted bandwidth situations, this
  commit allows the SRC_URI to point to a kernel tgz instead of a full git
  repository.

  Outside of the upstream tgz instead of a kernel git repository, the
  restrictions, config and patch process is the same as any linux-yocto-custom
  recipe.

  An example linux-yocto-custom based recipe would have a configuration like
  this to build the 3.7 kernel, using an externally supplied config, from the
  3.7 tgz:

    SRC_URI = "http://kernel.org/pub/linux/kernel/v3.0/linux-3.7.tar.bz2"
    PV = "3.7"
    S = "${WORKDIR}/linux-3.7"
    SRC_URI[md5sum] = "5323f3faadd051e83af605a63be5ea2e"
    SRC_URI[sha256sum] = "dc08d87a579fe2918362e6666e503a95a76296419195cb499aa9dd4dbe171a9e"

  [YOCTO #2686]

Cheers,

Bruce

The following changes since commit 828b1143477da079956a5541f8cc66c07ab6a3cc:

  multilib: skip packages that provide virtual/kernel (2013-01-31 12:39:47 -0500)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel-dev
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (5):
  guilt: remove GIT_EXEC_BASE export
  kernel-yocto: make configuration audit details debug only
  kernel-yocto: fix .scc and .cfg matching
  kernel-yocto: allow multiple / shared kernel feature directories
  kernel-yocto/linux-yocto-custom: support low bandwidth options

 meta/classes/kernel-yocto.bbclass                  |   77 +++++++++++++++-----
 meta/recipes-devtools/guilt/guilt-native_0.33.bb   |    3 +-
 .../kern-tools/kern-tools-native_git.bb            |    2 +-
 3 files changed, 62 insertions(+), 20 deletions(-)

-- 
1.7.10.4

[PATCH 1/5] guilt: remove GIT_EXEC_BASE export

[Bruce Ashfield]

git-core provides the following routines (among others): git-sh-setup,
cd_to_toplevel, die, and more.  But it is not always in the same location
relative to the guilt binary if git is not part of a 'host tools'
sysroot. Modern git versions don't need this, so commenting it out (until it
breaks again) is the solution to the problem of it not existing, and the
library routines will sourced and provided by git itself.

Since bitbake.conf has git-native as ASSUME_PROVIDED, this means that
when the system git binary is used, errors such as this can be seen in
failed patch logs:

| /opt/poky/build/tmp/sysroots/x86_64-linux/usr/bin/guilt: line 29: /opt/poky/build/tmp/sysroots/x86_64-linux/usr/bin/../libexec/git-core/git-sh-setup: No such file or directory
| /opt/poky/build/tmp/sysroots/x86_64-linux/usr/bin/guilt: line 717: cd_to_toplevel: command not found
| error: patch failed: Makefile:2
| error: Makefile: patch does not apply
| /opt/poky/build/tmp/sysroots/x86_64-linux/usr/bin/guilt-push: line 137: die: command not found
| [ERROR] unable to complete push
| pending patches are:
| /opt/poky/build/tmp/sysroots/x86_64-linux/usr/bin/guilt: line 29: /opt/poky/build/tmp/sysroots/x86_64-linux/usr/bin/../libexec/git-core/git-sh-setup: No such file or directory
| /opt/poky/build/tmp/sysroots/x86_64-linux/usr/bin/guilt: line 29: /opt/poky/build/tmp/sysroots/x86_64-linux/usr/bin/../libexec/git-core/git-sh-setup: No such file or directory
| links/linux-yocto-custom/0001-linux-version-tweak.patch
| ERROR. could not update git tree

With the export removed, we have a normal "clean" failure message when
the sysroot or system git is used.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/recipes-devtools/guilt/guilt-native_0.33.bb |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/guilt/guilt-native_0.33.bb b/meta/recipes-devtools/guilt/guilt-native_0.33.bb
index 6652ab6..d4dd616 100644
--- a/meta/recipes-devtools/guilt/guilt-native_0.33.bb
+++ b/meta/recipes-devtools/guilt/guilt-native_0.33.bb
@@ -4,7 +4,7 @@ LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = "file://COPYING;md5=b6f3400dc1a01cebafe8a52b3f344135"
 
 PV = "0.33"
-PR = "r3"
+PR = "r4"
 
 inherit native
 
@@ -18,7 +18,6 @@ SRC_URI = "http://ftp.de.debian.org/debian/pool/main/g/guilt/guilt_${PV}.orig.ta
 	   file://guilt-push-no-series.patch \
 	   file://make_git_commands_conditional.patch \
 	   file://improve_auto_header_gen.patch \
-	   file://guilt-set-git_exec_path.patch \
 	   file://guilt-bash.patch \
 	   file://guilt-update-supported-git-versions-to-1.8.x.patch \
 	   file://optional_head_check.patch"
-- 
1.7.10.4

[PATCH 2/5] kernel-yocto: make configuration audit details debug only

[Bruce Ashfield]

The details of the kernel configuration audit are typically a
debug action, so should be moved to bb.debug(). But in order
to maintain visibility of the results, a reference to the log
file is provided in the standard message.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/classes/kernel-yocto.bbclass |    8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index aaee441..b336e43 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -207,7 +207,7 @@ do_kernel_configme() {
 python do_kernel_configcheck() {
     import re, string, sys, commands
 
-    bb.plain("NOTE: validating kernel configuration")
+    bb.plain("NOTE: validating kernel config, see log.do_kernel_configcheck for details")
 
     # if KMETA isn't set globally by a recipe using this routine, we need to
     # set the default to 'meta'. Otherwise, kconf_check is not passed a valid
@@ -218,7 +218,11 @@ python do_kernel_configcheck() {
     cmd = d.expand("cd ${S}; kconf_check -config- %s/meta-series ${S} ${B}" % kmeta)
     ret, result = commands.getstatusoutput("%s%s" % (pathprefix, cmd))
 
-    bb.plain( "%s" % result )
+    config_check_visibility = d.getVar( "KCONF_AUDIT_LEVEL", True ) or 1
+    if config_check_visibility == 1:
+        bb.debug( 1, "%s" % result )
+    else:
+        bb.note( "%s" % result )
 }
 
 # Ensure that the branches (BSP and meta) are on the locations specified by
-- 
1.7.10.4

[PATCH 3/5] kernel-yocto: fix .scc and .cfg matching

[Bruce Ashfield]

SRC_URIs that contained git repositories or other constructs that resulted
in an extension of "." or a substring of "scc" or "cfg" were matching the
tests for patches and configs. This was due to a python tuple being used
instead of an array. Switching to an array makes the match exact and the
behaviour we want.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/classes/kernel-yocto.bbclass |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index b336e43..962b493 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -20,7 +20,7 @@ def find_sccs(d):
     sources_list=[]
     for s in sources:
         base, ext = os.path.splitext(os.path.basename(s))
-        if ext and ext in ('.scc' '.cfg'):
+        if ext and ext in [".scc", ".cfg"]:
             sources_list.append(s)
         elif base and base in 'defconfig':
             sources_list.append(s)
-- 
1.7.10.4

[PATCH 4/5] kernel-yocto: allow multiple / shared kernel feature directories

[Bruce Ashfield]

To promote the reuse and sharing of configuration fragments this change
allows any kernel-yocto based recipe to have multiple alternate git repositories
which provide kernel feature directory trees listed on the SRC_URI.

These feature directories are in addition to any in-tree kernel meta data branches
that may be available (described via the KMETA variable in linux-yocto recipes).

Features found within these directories can be used from recipes via the
KERNEL_FEATURES variable. Features found within a feature directory are free
to include any other features that are available in any directories. In both
cases the path to a feature description (a .scc file) is relative to the
root of a given feature directory (which is how existing .scc files work)

The search order for features is determined by the order that repositories
appear on the SRC_URI.

Normal SRC_URI rules apply to any repository that is added as a kernel
feature container. A SRCREV must be supplied and it must be unpacked to
a unique directory, which is controlled via the "destsuffic" url parameter.

In addition to these standard requirements, any kernel feature repository
reference should identify itself via the "type=kmeta" url parameter. If
type=kmeta is not supplied, the repository will not be processed for
kernel features.

As an example, the following in a linux-yocto bbappend makes two additional
feature directories available to KERNEL_FEATURES and fragments.

 SRC_URI += "git://git.yoctoproject.org/yocto-kernel-cache;protocol=git;branch=master;type=kmeta;name=feat1;destsuffix=kernel-cache/"
 SRC_URI += "git://${KSRC_linux_yocto_3_4};protocol=file;branch=meta;name=feat2;type=kmeta;destsuffix=kernel-features-experimental/"

 SRCREV_feat1 = "${AUTOREV}"
 SRCREV_feat2 = "${AUTOREV}"

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/classes/kernel-yocto.bbclass                  |   33 +++++++++++++++++++-
 .../kern-tools/kern-tools-native_git.bb            |    2 +-
 2 files changed, 33 insertions(+), 2 deletions(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index 962b493..92ede6a 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -42,6 +42,23 @@ def find_urls(d):
 
     return patch_list
 
+# check the SRC_URI for "kmeta" type'd git repositories. Return the name of
+# the repository as it will be found in WORKDIR
+def find_kernel_feature_dirs(d):
+    feature_dirs=[]
+    fetch = bb.fetch2.Fetch([], d)
+    for url in fetch.urls:
+        urldata = fetch.ud[url]
+        parm = urldata.parm
+        if "type" in parm:
+            type = parm["type"]
+        if "destsuffix" in parm:
+            destdir = parm["destsuffix"]
+            if type == "kmeta":
+                feature_dirs.append(destdir)
+	    
+    return feature_dirs
+
 
 do_patch() {
 	cd ${S}
@@ -72,6 +89,7 @@ do_patch() {
 
 	sccs="${@" ".join(find_sccs(d))}"
 	patches="${@" ".join(find_patches(d))}"
+	feat_dirs="${@" ".join(find_kernel_feature_dirs(d))}"
 
 	set +e
 	# add any explicitly referenced features onto the end of the feature
@@ -82,13 +100,26 @@ do_patch() {
 		done
 	fi
 
+	# check for feature directories/repos/branches that were part of the
+	# SRC_URI. If they were supplied, we convert them into include directives
+	# for the update part of the process
+	if [ -n "${feat_dirs}" ]; then
+	    for f in ${feat_dirs}; do
+		if [ -d "${WORKDIR}/$f/meta" ]; then
+		    includes="$includes -I${WORKDIR}/$f/meta"
+		elif [ -d "${WORKDIR}/$f" ]; then
+		    includes="$includes -I${WORKDIR}/$f"
+		fi
+	    done
+	fi
+
 	if [ "${kbranch}" != "${KBRANCH_DEFAULT}" ]; then
 		updateme_flags="--branch ${kbranch}"
 	fi
 
 	# updates or generates the target description
 	updateme ${updateme_flags} -DKDESC=${KMACHINE}:${LINUX_KERNEL_TYPE} \
-                           ${addon_features} ${ARCH} ${KMACHINE} ${sccs} ${patches}
+                         ${includes} ${addon_features} ${ARCH} ${KMACHINE} ${sccs} ${patches}
 	if [ $? -ne 0 ]; then
 		echo "ERROR. Could not update ${kbranch}"
 		exit 1
diff --git a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
index 635dfe6..98cd8b9 100644
--- a/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
+++ b/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb
@@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70c
 
 DEPENDS = "git-native guilt-native"
 
-SRCREV = "62c8807825ea923a18b1519375b0df67ad9daf2b"
+SRCREV = "9284af9b968d40e441b10f5c09961cbe329ccb9b"
 PR = "r12"
 PV = "0.1+git${SRCPV}"
 
-- 
1.7.10.4

[PATCH 5/5] kernel-yocto/linux-yocto-custom: support low bandwidth options

[Bruce Ashfield]

To support configurations where active development is not being done within
the oe/bitbake build environment and restricted bandwidth situations, this
commit allows the SRC_URI to point to a kernel tgz instead of a full git
repository.

Outside of the upstream tgz instead of a kernel git repository, the
restrictions, config and patch process is the same as any linux-yocto-custom
recipe.

An example linux-yocto-custom based recipe would have a configuration like
this to build the 3.7 kernel, using an externally supplied config, from the
3.7 tgz:

  SRC_URI = "http://kernel.org/pub/linux/kernel/v3.0/linux-3.7.tar.bz2"
  PV = "3.7"
  S = "${WORKDIR}/linux-3.7"
  SRC_URI[md5sum] = "5323f3faadd051e83af605a63be5ea2e"
  SRC_URI[sha256sum] = "dc08d87a579fe2918362e6666e503a95a76296419195cb499aa9dd4dbe171a9e"

[YOCTO #2686]

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/classes/kernel-yocto.bbclass |   34 +++++++++++++++++++++-------------
 1 file changed, 21 insertions(+), 13 deletions(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index 92ede6a..8494c16 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -158,22 +158,10 @@ do_kernel_checkout() {
 		mkdir -p ${S}
 		
 		# We can fix up the kernel repository even if it wasn't a bare clone.
-		# If KMETA is defined, the branch must exist, but a machine branch
-		# can be missing since it may be created later by the tools.
 		mv ${WORKDIR}/git/.git ${S}
 		rm -rf ${WORKDIR}/git/
 		cd ${S}
-		if [ -n "${KMETA}" ]; then
-			git branch -a | grep -q ${KMETA}
-			if [ $? -ne 0 ]; then
-				echo "ERROR. The branch '${KMETA}' is required and was not"
-				echo "found. Ensure that the SRC_URI points to a valid linux-yocto"
-				echo "kernel repository"
-				exit 1
-			fi
-		fi
-	fi
-	if [ -d "${WORKDIR}/git/" ] && [ ! -d "${WORKDIR}/git/.git" ]; then
+	elif [ -d "${WORKDIR}/git/" ] && [ ! -d "${WORKDIR}/git/.git" ]; then
 		# we build out of {S}, so ensure that ${S} is clean and present
 		rm -rf ${S}
 		mkdir -p ${S}/.git
@@ -182,9 +170,29 @@ do_kernel_checkout() {
 		rm -rf ${WORKDIR}/git/
 		cd ${S}	
 		git config core.bare false
+	else
+	        # We have no git repository at all. To support low bandwidth options
+		# for building the kernel, we'll just convert the tree to a git repo
+	        # and let the rest of the process work unchanged
+	        cd ${S}
+		git init
+		git add .
+		git commit -q -m "baseline commit: creating repo for ${PN}-${PV}"
 	fi
 	# end debare
 
+       	# If KMETA is defined, the branch must exist, but a machine branch
+	# can be missing since it may be created later by the tools.
+	if [ -n "${KMETA}" ]; then
+		git branch -a | grep -q ${KMETA}
+		if [ $? -ne 0 ]; then
+			echo "ERROR. The branch '${KMETA}' is required and was not"
+			echo "found. Ensure that the SRC_URI points to a valid linux-yocto"
+			echo "kernel repository"
+			exit 1
+		fi
+	fi
+
 	# convert any remote branches to local tracking ones
 	for i in `git branch -a | grep remotes | grep -v HEAD`; do
 		b=`echo $i | cut -d' ' -f2 | sed 's%remotes/origin/%%'`;
-- 
1.7.10.4

[PATCH 0/5] kernel-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

Here are some fixes for the minor issues cased by the kern-tools update
and the recent 4.8 kernel introduction.

RP reported a build and footprint time increase for 4.8, that was due to
some missing kernel meta data that (re)enabled DEBUG and for the standard
kernel. commit [kernel-yocto: restore missing configuration meta data]
deals with that issue.

The commits:

  kernel-yocto: restore kernel-meta data detection for SRC_URI elements
  kernel-yocto: allow --allnoconfig and --alldefconfig as KCONFIG_MODES

Fix some issues with the compatibility of existing layers and config
fragment users. I was luckily able to fix the issues without bringing
the complexity that I was removing.

There's a small change to uvesafb to have a longer timeout on some
machines (or virtual machines) to avoid issues when performing QA
testing.

And finally, we have the 4.8-rc5 content update. I'll do one of these
a week until we get to the full 4.8 release. This can be pended for
the M3 build, but it did pass my local sanity testing.

Cheers,

Bruce

The following changes since commit ce4ea7a730a7bec257218533b7c1fcb31134e25b:

  recipetool: create: avoid extra blank lines in output recipe (2016-09-08 00:36:49 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (5):
  kernel-yocto: restore kernel-meta data detection for SRC_URI elements
  kernel-yocto: allow --allnoconfig and --alldefconfig as KCONFIG_MODES
  kernel-yocto: restore missing configuration meta data
  linux-yocto: update to 4.8-rc5
  linux-yocto/4.4/4.8: uvesafb: provide option to specify timeout for
    task completion

 meta/classes/kernel-yocto.bbclass                 | 15 ++++++++++-----
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb   |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb |  4 ++--
 meta/recipes-kernel/linux/linux-yocto_4.4.bb      | 18 +++++++++---------
 meta/recipes-kernel/linux/linux-yocto_4.8.bb      | 18 +++++++++---------
 7 files changed, 36 insertions(+), 31 deletions(-)

-- 
2.5.0

[PATCH 0/5] kernel-yocto: consolidated pull request

[Bruce Ashfield]

Hi all,

Here is my latest set of updates to the 4.8/4.4 kernels, as well as a couple
of bug fixes to the tools.

I've included short log summaries of the changes that come with the -stable
updates in the commits themselves.

Also of note, now that 4.9 is in the latter part of the -rc cycle, I'll bring
linux-yocto-dev up to date with it, and create a versioned recipe for it, so
it can be the LTS kernel in the 2.3 release.

Cheers,

Bruce

The following changes since commit 9b1bd29ea99aa0dec51e603e4ac28e211af19765:

  maintainers.inc: remove libwnck3 recipe (2016-11-15 15:19:55 +0000)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib zedd/kernel
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (5):
  linux-yocto/4.8: fix cryptodev compilation error
  linux-yocto/4.8: update to v4.8.6-rt5
  linux-yocto/4.8: update from v4.8.6 -> v4.8.8
  linux-yocto/4.4: update to v4.4.32
  kern-tools: error checking and tree generation fixes

 .../kern-tools/kern-tools-native_git.bb              |  2 +-
 meta/recipes-kernel/linux/linux-yocto-rt_4.4.bb      |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-rt_4.8.bb      |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb    |  6 +++---
 meta/recipes-kernel/linux/linux-yocto-tiny_4.8.bb    |  6 +++---
 meta/recipes-kernel/linux/linux-yocto_4.4.bb         | 20 ++++++++++----------
 meta/recipes-kernel/linux/linux-yocto_4.8.bb         | 20 ++++++++++----------
 7 files changed, 33 insertions(+), 33 deletions(-)

-- 
2.5.0

[PATCH 0/5] kernel-yocto: consolidated pull request

[Bruce Ashfield]

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

Richard,

Here's the latest set of queued kernel changes.

Two are routine -stable updates, the other meta data change is the cherry pick
of a 5.4 change we had, that I somehow missed when creating the 5.8 config
branch. This will get rid of he intermittent reproducibility failure, which
I'll continue to debug.

The two kernel-yocto changes are features that have been requested for some
time. One simply allows an configuration audit warning to be an error (off by
default), and the other allows changes to files pointed to by .scc files to
be part of the checksum.

I checked the checksum patch as discussed earlier, and it does look like it
will work with directories that don't already exist, since if something isn't
listed already as :True, it will be added as either :True or :False based on
whether it exists when the checksum is calculated.

There's a corner case that a moved file doesn't seen to trigger a new exec of
the task, but that isn't something commonly done and something that I can look
into if it pops up. I've had this patch in my tree for ~8 months, so it is
time to get it out and about :D

Cheers,

Bruce

The following changes since commit b67303460c9da25f69b206d0bbb3fa1467857bab:

  devtool: expand SRC_URI when guessing recipe update mode (2020-08-27 08:28:03 +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 (5):
  linux-yocto/5.4: update to v5.4.61
  linux-yocto/5.8: update to v5.8.4
  linux-yocto/5.8: disable IKHEADERS in default builds
  kernel-yocto: checksum all modifications to available kernel fragments
    directories
  kernel-yocto: allow promotion of configuration warnings to errors

 meta/classes/kernel-yocto.bbclass             | 52 ++++++++++++++++++-
 .../linux/linux-yocto-rt_5.4.bb               |  6 +--
 .../linux/linux-yocto-rt_5.8.bb               |  6 +--
 .../linux/linux-yocto-tiny_5.4.bb             |  8 +--
 .../linux/linux-yocto-tiny_5.8.bb             |  8 +--
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 ++++----
 meta/recipes-kernel/linux/linux-yocto_5.8.bb  | 22 ++++----
 7 files changed, 86 insertions(+), 38 deletions(-)

-- 
2.19.1

[PATCH 0/5] kernel-yocto: consolidated pull request

[bruce.ashfield]

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

Richard,

Here's the next round of -stable updates, and a lttng-modules fix .. just
because what fun would it be without some lttng issues :)

Local testing has passed, but we'll see if the AB manages to spot something
that I could hit.

Bruce

The following changes since commit bd66a18eaa463c2eab291fea68039bf0d61c7b8b:

  openssl: minor security upgrade 3.0.2 -> 3.0.3 (2022-05-15 08:57:16 +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 (5):
  linux-yocto/5.15: update to v5.15.37
  linux-yocto/5.10: update to v5.10.113
  linux-yocto/5.15: update to v5.15.38
  linux-yocto/5.10: update to v5.10.114
  lttng-modules: fix build against 5.18-rc7+

 .../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 | 24 ++---
 meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 +++---
 ...x-__trace_sched_switch_state-5.18-rc.patch | 88 +++++++++++++++++++
 .../lttng/lttng-modules_2.13.3.bb             |  1 +
 8 files changed, 127 insertions(+), 38 deletions(-)
 create mode 100644 meta/recipes-kernel/lttng/lttng-modules/0001-sched-tracing-fix-__trace_sched_switch_state-5.18-rc.patch

-- 
2.19.1

[PATCH 0/5] kernel-yocto: consolidated pull request

[bruce.ashfield]

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

Richard,

A dev kernel bump to 6.10 will follow this, but I still have it under
test.

I've built core-image-kernel-dev and minimal for multiple architectures
against both musl and glibc for the kernel headers and I didn't find
any issues. Fingers crossed the AB doesn't find something I missed.

-stable updates for the LTS branches will follow in a few more days.

Cheers,

Bruce

The following changes since commit f66f8fa9f605d5dc39acb10226198b3ab40dcaa3:

  oe-build-perf-report: Add commit hash link to chart tooltip (2024-05-24 16:59:31 +0100)

are available in the Git repository at:

  https://git.yoctoproject.org/poky-contrib zedd/kernel
  https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (5):
  linux-yocto/6.6: update to v6.6.30
  linux-yocto/6.6: intel configuration changes
  linux-libc-headers: bump to v6.9
  linux-yocto/6.6: update to v6.6.32
  linux-yocto/6.6: cfg: introduce Intel NPU fragment

 meta/conf/distro/include/tcmode-default.inc   |  2 +-
 ...aders_6.6.bb => linux-libc-headers_6.9.bb} |  2 +-
 .../linux/linux-yocto-rt_6.6.bb               |  6 ++--
 .../linux/linux-yocto-tiny_6.6.bb             |  6 ++--
 meta/recipes-kernel/linux/linux-yocto_6.6.bb  | 28 +++++++++----------
 5 files changed, 22 insertions(+), 22 deletions(-)
 rename meta/recipes-kernel/linux-libc-headers/{linux-libc-headers_6.6.bb => linux-libc-headers_6.9.bb} (83%)

-- 
2.39.2

[PATCH 0/5] kernel-yocto: consolidated pull request

[bruce.ashfield]

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

Richard,

Here's the next set of -stable updates for the kernel's in master.

I'm continuing to watch 6.10 in case we need to jump to 6.11 for
the release.

-stable updates for the other branches will be sent shortly as
well.

Bruce


The following changes since commit bd2159719c08c101a25a5012fc684163135653e6:

  patchtest: test_non_auh_upgrade: improve parse logic (2024-09-01 12:32:37 +0100)

are available in the Git repository at:

  https://git.yoctoproject.org/poky-contrib zedd/kernel
  https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (5):
  linux-yocto/6.6: update to v6.6.47
  linux-yocto/6.10: fix CONFIG_PWM_SYSFS config warning
  linux-yocto/6.10: update to v6.10.7
  linux-yocto/6.10: update to v6.10.8
  linux-yocto/6.6: update to v6.6.49

 .../linux/linux-yocto-rt_6.10.bb              |  6 ++--
 .../linux/linux-yocto-rt_6.6.bb               |  6 ++--
 .../linux/linux-yocto-tiny_6.10.bb            |  6 ++--
 .../linux/linux-yocto-tiny_6.6.bb             |  6 ++--
 meta/recipes-kernel/linux/linux-yocto_6.10.bb | 28 +++++++++----------
 meta/recipes-kernel/linux/linux-yocto_6.6.bb  | 28 +++++++++----------
 6 files changed, 40 insertions(+), 40 deletions(-)

-- 
2.39.2

[PATCH 0/5] kernel-yocto: consolidated pull request

[bruce.ashfield]

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

Richard,

Here's the final preparation patch for the LTS release and
reference kernel versions.

I've tested 6.13 in linux-yocto-dev and it passed, I've moved
onto 6.14, so I'll update to it for the dev kernel in the
release, but that comes later this week as my testing has a
few issues I need to look into.

I removed the 6.6 references I found, and updated thing to
6.12 .. but I could have missed something, but they are an
easy fix if the AB does trip over something.

I also found a stale 6.10 cve file, so I'm removing it in this
series.

These are on top of poky and a single series, since it is
easier than two separate sends on top of OE core and poky,
but if we'd rather they be split, I can do that.

Bruce

The following changes since commit 4f6b1440af3eb7c4b659d9b0329592180ccea5fe:

  scripts/buildperf: Add chart tabs for commit count/time (2025-02-09 18:42:48 -0500)

are available in the Git repository at:

  https://git.yoctoproject.org/poky-contrib zedd/kernel
  https://git.yoctoproject.org/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (5):
  kernel: drop 6.6 reference kernels
  kernel: remove unused 6.10 CVE exclusion file
  linux-yocto/6.12: update to v6.12.12
  poky-alt: switch preferred kernel to 6.12
  yocto-bsp: drop linux-yocto 6.6 bbappend

 .../include/poky-distro-alt-test-config.inc   |    2 +-
 .../linux/linux-yocto_6.6.bbappend            |   21 -
 .../linux/cve-exclusion_6.10.inc              | 6660 -----------------
 .../linux/cve-exclusion_6.6.inc               | 6660 -----------------
 .../linux/linux-yocto-rt_6.12.bb              |    6 +-
 .../linux/linux-yocto-rt_6.6.bb               |   48 -
 .../linux/linux-yocto-tiny_6.12.bb            |    6 +-
 .../linux/linux-yocto-tiny_6.6.bb             |   33 -
 meta/recipes-kernel/linux/linux-yocto_6.12.bb |   28 +-
 meta/recipes-kernel/linux/linux-yocto_6.6.bb  |   74 -
 10 files changed, 21 insertions(+), 13517 deletions(-)
 delete mode 100644 meta-yocto-bsp/recipes-kernel/linux/linux-yocto_6.6.bbappend
 delete mode 100644 meta/recipes-kernel/linux/cve-exclusion_6.10.inc
 delete mode 100644 meta/recipes-kernel/linux/cve-exclusion_6.6.inc
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-rt_6.6.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_6.6.bb
 delete mode 100644 meta/recipes-kernel/linux/linux-yocto_6.6.bb

-- 
2.39.2