Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bob Cochran <openembedded@mindchasers.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] kernel.bbclass: change oldnoconfig to olddefconfig
Date: Fri,  9 Jan 2015 13:04:33 -0500	[thread overview]
Message-ID: <1420826673-9471-1-git-send-email-openembedded@mindchasers.com> (raw)

KERNEL_CONFIG_COMMAND is defined as passing oldnoconfig to
oe_runmake_call, but oldnoconfig is both an alias to olddefconfig and a
misleading name.  Therefore, change it to the meaningfully named
option: olddefconfig.

For further background, please see commit fb16d8912db5268f29706010ecafff74b971c58d  in
Linux kernel source tree:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=fb16d8912db5268f29706010ecafff74b971c58d

Signed-off-by: Bob Cochran <openembedded@mindchasers.com>
---
 meta/classes/kernel.bbclass |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 88356b1..aebbc65 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -275,7 +275,7 @@ python sysroot_stage_all () {
     oe.path.copyhardlinktree(d.expand("${D}${KERNEL_SRC_PATH}"), d.expand("${SYSROOT_DESTDIR}${KERNEL_SRC_PATH}"))
 }
 
-KERNEL_CONFIG_COMMAND ?= "oe_runmake_call -C ${S} O=${B} oldnoconfig || yes '' | oe_runmake -C ${S} O=${B} oldconfig"
+KERNEL_CONFIG_COMMAND ?= "oe_runmake_call -C ${S} O=${B} olddefconfig || yes '' | oe_runmake -C ${S} O=${B} oldconfig"
 
 kernel_do_configure() {
 	# fixes extra + in /lib/modules/2.6.37+
-- 
1.7.9.5



             reply	other threads:[~2015-01-09 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 18:04 Bob Cochran [this message]
2015-01-09 19:08 ` [PATCH] kernel.bbclass: change oldnoconfig to olddefconfig 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=1420826673-9471-1-git-send-email-openembedded@mindchasers.com \
    --to=openembedded@mindchasers.com \
    --cc=openembedded-core@lists.openembedded.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