From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 3/8] kern-tools: non-gcc config support and option re-classification
Date: Mon, 14 Dec 2020 10:09:19 -0500 [thread overview]
Message-ID: <b4e15cbba75d1832e39c334a4e3b0798ccea74b8.1607958349.git.bruce.ashfield@gmail.com> (raw)
In-Reply-To: <cover.1607958349.git.bruce.ashfield@gmail.com>
From: Bruce Ashfield <bruce.ashfield@gmail.com>
Integrating the following commits:
1aa9046 merge_config.sh: Translate some env variables to make variables
6fdcd64 symbol_why: allow re-classification from non-hardare to hardware
With these, a non-gcc compiler can be used, since the invocation of the
kernel configuration explicitly passes the variables as command line
vars, versus environment variables. This means the kernel Makefile
assignments are overriden and the desired compiler used.
With option re-classification, we can inhibit warnings when an option
has incorrectly been classified has 'hardware', and hence triggers a
visible warning.
[merge_config.sh: Translate some env variables to make variables]
Signed-off-by: Tyler Hicks <tyhicks@linux.microsoft.com>
[symbol_why: allow re-classification from non-hardare to hardware]
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
meta/recipes-kernel/kern-tools/kern-tools-native_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 ea33732a3e..d2dfd8c8a8 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://tools/kgit;beginline=5;endline=9;md5=9c30e971d435e249
DEPENDS = "git-native"
-SRCREV = "df4390b18a500a1a7d4695e1856971f8e36ce517"
+SRCREV = "1aa90463ad5d63f51aeeefed84fd6618b17da157"
PR = "r12"
PV = "0.2+git${SRCPV}"
--
2.19.1
next prev parent reply other threads:[~2020-12-14 15:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 15:09 [PATCH 0/8] linux-yocto: consolidated pull requesrt Bruce Ashfield
2020-12-14 15:09 ` [PATCH 1/8] linux-yocto-rt/5.4: update to -rt44 Bruce Ashfield
2020-12-14 15:09 ` [PATCH 2/8] linux-yocto/5.4: update to v5.4.80 Bruce Ashfield
2020-12-14 15:09 ` Bruce Ashfield [this message]
2020-12-14 15:09 ` [PATCH 4/8] linux-yocto/cfg: qemuppc: set CONFIG_SCSI to '=y' Bruce Ashfield
2020-12-14 15:09 ` [PATCH 5/8] linux-yocto/5.4: update to v5.4.82 Bruce Ashfield
2020-12-14 15:09 ` [PATCH 6/8] linux-yocto/cfg: qemuarm64-gfx.cfg: add CONFIG_INPUT_UINPUT Bruce Ashfield
2020-12-14 15:09 ` [PATCH 7/8] lttng-modules: fix build against v5.10+ Bruce Ashfield
2020-12-14 15:09 ` [PATCH 8/8] linux-yocto/5.4: update to v5.4.83 Bruce Ashfield
2020-12-19 11:31 ` [PATCH 0/8] linux-yocto: consolidated pull requesrt Richard Purdie
2020-12-19 15:48 ` Bruce Ashfield
2020-12-19 15:52 ` Richard Purdie
2020-12-19 16:04 ` Bruce Ashfield
2020-12-21 2:57 ` [OE-core] " Anuj Mittal
2020-12-21 3:34 ` 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=b4e15cbba75d1832e39c334a4e3b0798ccea74b8.1607958349.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox