All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>,
	"João Henrique Ferreira de Freitas" <joaohf@gmail.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [yocto-docs][PATCH] kernel-dev: Updates "Generating Configuration Files" section
Date: Mon, 10 Mar 2014 15:59:57 -0800	[thread overview]
Message-ID: <CF4391B9.7632F%dvhart@linux.intel.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237983F79BAB@ORSMSX101.amr.corp.intel.com>

On 3/10/14, 14:55, "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
wrote:

>Yes - the manual for 1.6 is only for that release.  I would have to take
>separate steps to apply it to dora or Dylan branches.

The point there being that someone reading the current manual and working
on the 1.5 releases, would find these proposed changes will fail. The
method being removed here would work on all versions since this document
was created.

--
Darren

>
>>-----Original Message-----
>>From: Darren Hart [mailto:dvhart@linux.intel.com]
>>Sent: Monday, March 10, 2014 4:52 PM
>>To: João Henrique Ferreira de Freitas; yocto@yoctoproject.org
>>Cc: Rifenbark, Scott M
>>Subject: Re: [yocto] [yocto-docs][PATCH] kernel-dev: Updates "Generating
>>Configuration Files" section
>>
>>On 3/5/14, 18:20, "João Henrique Ferreira de Freitas" <joaohf@gmail.com>
>>wrote:
>>
>>>Add a new step about how to use diffconfig task to create kernel config
>>>fragments.
>>>
>>>[YOCTO #3862]
>>>
>>>Signed-off-by: João Henrique Ferreira de Freitas <joaohf@gmail.com>
>>
>>Thank you for updating the documentation. Please Cc: the relevant parties
>>with patches to the list (the author for one, and a git log would reveal
>>Scott R.
>>as the next obvious owner).
>>
>>Scott, This is good stuff to add. My only thought is this is new
>>functionality, the
>>old method is still valid - and necessary before 1.6.
>>What are your thoughts on dealing with this? Does the manual with 1.6
>>ONLY
>>apply to 1.6?
>>
>>--
>>Darren
>>
>>>---
>>> documentation/kernel-dev/kernel-dev-common.xml | 25
>>>+++++++++----------------
>>> 1 file changed, 9 insertions(+), 16 deletions(-)
>>>
>>>diff --git a/documentation/kernel-dev/kernel-dev-common.xml
>>>b/documentation/kernel-dev/kernel-dev-common.xml
>>>index a152f9f..de04a39 100644
>>>--- a/documentation/kernel-dev/kernel-dev-common.xml
>>>+++ b/documentation/kernel-dev/kernel-dev-common.xml
>>>@@ -342,32 +342,25 @@
>>>                         <literallayout class='monospaced'>
>>>      $ bitbake linux-yocto -c kernel_configme -f
>>>                         </literallayout></para></listitem>
>>>-                    <listitem><para>Copy and rename the resulting
>>>-                        <filename>.config</filename> file (e.g.
>>>-                        <filename>config.orig</filename>).
>>>-                        </para></listitem>
>>>                     <listitem><para>Run the
>>><filename>menuconfig</filename>
>>>                         command:
>>>                         <literallayout class='monospaced'>
>>>      $ bitbake linux-yocto -c menuconfig
>>>                         </literallayout></para></listitem>
>>>-                    <listitem><para>Prepare a configuration fragment
>>>based on
>>>-                        the differences between the two files.
>>>-                        </para></listitem>
>>>+                    <listitem><para>Run the
>>><filename>diffconfig</filename>
>>>+                        command to prepare a configuration fragment.
>>>+                        The result file
>>><filename>fragment.cfg</filename> will be placed in
>>>+                        <filename>${</filename><ulink
>>>url='&YOCTO_DOCS_REF_URL;#var-
>>WORKDIR'><filename>WORKDIR</filename></ul
>>>ink
>>>><filename>}</filename> directory:
>>>+                        <literallayout class='monospaced'>
>>>+     $ bitbake linux-yocto -c diffconfig
>>>+                        </literallayout></para></listitem>
>>>                 </orderedlist>
>>>             </para>
>>>
>>>             <para>
>>>-                Ultimately, the configuration fragment file needs to
>>>be a
>>>+                The <filename>diffconfig</filename> command creates a
>>>file that is a
>>>                 list of Linux kernel <filename>CONFIG_</filename>
>>>assignments.
>>>-                It cannot be in <filename>diff</filename> format.
>>>-                Here is an example of a command that creates your
>>>-                configuration fragment file.
>>>-                Regardless of the exact command you use, plan on
>>>reviewing
>>>-                the output as you can usually remove some of the
>>>defaults:
>>>-                <literallayout class='monospaced'>
>>>-     $ diff -Nurp config.orig .config | sed -n "s/^\+//p" > frag.cfg
>>>-                </literallayout>
>>>+
>>>                 See the "<link
>>>linkend='changing-the-configuration'>Changing the Configuration</link>"
>>>                 section for information on how to use the output as a
>>>                 configuration fragment.
>>>--
>>>1.8.3.2
>>>
>>>_______________________________________________
>>>yocto mailing list
>>>yocto@yoctoproject.org
>>>https://lists.yoctoproject.org/listinfo/yocto
>>>
>>
>>
>>--
>>Darren Hart
>>Yocto Project - Linux Kernel
>>Intel Open Source Technology Center
>>
>>
>>
>
>


-- 
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center






  reply	other threads:[~2014-03-10 22:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06  2:20 [yocto-docs][PATCH] kernel-dev: Updates "Generating Configuration Files" section João Henrique Ferreira de Freitas
2014-03-10 23:52 ` Darren Hart
2014-03-10 22:55   ` Rifenbark, Scott M
2014-03-10 23:59     ` Darren Hart [this message]
2014-03-10 23:02       ` Rifenbark, Scott M
2014-03-11  0:47         ` Darren Hart
2014-03-10 23:57           ` Rifenbark, Scott M

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=CF4391B9.7632F%dvhart@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=joaohf@gmail.com \
    --cc=scott.m.rifenbark@intel.com \
    --cc=yocto@yoctoproject.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.