Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "João Henrique Ferreira de Freitas" <joaohf@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: dvhart@linux.intel.com
Subject: [PATCH 1/2] kernel-yocto: Add do_fragmentconfig task
Date: Wed, 12 Feb 2014 22:20:18 -0200	[thread overview]
Message-ID: <1392250819-10123-2-git-send-email-joaohf@gmail.com> (raw)
In-Reply-To: <1392250819-10123-1-git-send-email-joaohf@gmail.com>

Instead of using 'diff' command between two kernel config files,
the task fragmentconfig does the job creating the file
$WORKDIR/fragment.cfg that user should review and use.

[YOCTO #3862]

Signed-off-by: João Henrique Ferreira de Freitas <joaohf@gmail.com>
---
 meta/classes/kernel-yocto.bbclass | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index 8f79932..6597e54 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -411,3 +411,5 @@ do_kernel_link_vmlinux() {
 OE_TERMINAL_EXPORTS += "GUILT_BASE KBUILD_OUTPUT"
 GUILT_BASE = "meta"
 KBUILD_OUTPUT = "${B}"
+
+do_fragmentconfig[depends] += "virtual/kernel:do_kernel_configme"
-- 
1.8.3.2



  reply	other threads:[~2014-02-13  0:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13  0:20 [PATCH 0/2] Add task to create kernel config fragments João Henrique Ferreira de Freitas
2014-02-13  0:20 ` João Henrique Ferreira de Freitas [this message]
2014-02-13  0:20 ` [PATCH 2/2] cml1.bbclass: Add fragmentconfig task to cml1 João Henrique Ferreira de Freitas
2014-02-13  0:45   ` Darren Hart
2014-02-15 23:51     ` João Henrique Ferreira de Freitas
2014-02-13 11:33   ` Richard Purdie
2014-02-13 19:00     ` Darren Hart
2014-02-14 15:46       ` Richard Purdie
2014-02-14 16:15         ` Darren Hart
2014-02-14 16:44           ` Richard Purdie

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=1392250819-10123-2-git-send-email-joaohf@gmail.com \
    --to=joaohf@gmail.com \
    --cc=dvhart@linux.intel.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