All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <darren.hart@intel.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [PATCH 1/1] btrfs: Add a new kernel feature to enable the btrfs support
Date: Fri, 09 Sep 2011 14:09:21 -0700	[thread overview]
Message-ID: <4E6A8081.90605@intel.com> (raw)
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94DF053854@orsmsx504.amr.corp.intel.com>

On 09/09/2011 09:14 AM, Kamble, Nitin A wrote:
> Thanks Bruce, BTW we should enable this btrfs feature for
> linux-yocto-3 kernel. What is the right way to do it? Shall I send a
> patch for the Linux-yocot-3.0 recipe in the oe-core repository?

Hi Nitin,

Having a config fragment for btrfs available in linux-yocto is
appropriate and makes btrfs easily added to any BSP from recipe space or
from the linux-yocto meta repository.

However, we do not want to enable it by default for all linux-yocto
BSPs. Unless a device requires a specific FS to boot (fat, jffs2, etc) I
am happy to stick with ext3/4 for now. If you have a compelling reason
to enable btrfs for all embedded platforms, we can reconsider.

This does highlight a TODO for the kernel team. We need to define and
make readily available a Yocto Project Kernel Policy. This should
identify the non-hardware-specific CONFIG options that will be enabled
in any linux-yocto BSP config by default. We have discussed this some at
LPC already, and will continue to flesh it out.

Thanks,

Darren

> 
> Thanks, Nitin
> 
> 
>> -----Original Message----- From: Bruce Ashfield
>> [mailto:bruce.ashfield@windriver.com] Sent: Tuesday, September 06,
>> 2011 1:30 PM To: Kamble, Nitin A Cc: yocto@yoctoproject.org 
>> Subject: Re: [yocto] [PATCH 1/1] btrfs: Add a new kernel feature
>> to enable the btrfs support
>> 
>> On 11-09-06 03:56 PM, nitin.a.kamble@intel.com wrote:
>>> From: Nitin A Kamble<nitin.a.kamble@intel.com>
>> 
>> Looks good. If we are merging this as config only, I've been 
>> putting them in meta/cfg/kernel-cache/cfg/
>> 
>> So I relocated this configuration to that directory. I'll have it
>> pushed out in the next day or so (I'm getting on a plane shortly).
>> 
>> Bruce
>> 
>>> 
>>> Signed-off-by: Nitin A Kamble<nitin.a.kamble@intel.com> --- 
>>> meta/cfg/kernel-cache/features/btrfs/btrfs.cfg |    1 + 
>>> meta/cfg/kernel-cache/features/btrfs/btrfs.scc |    1 + 2 files
>>> changed, 2 insertions(+), 0 deletions(-) create mode 100644
>>> meta/cfg/kernel-cache/features/btrfs/btrfs.cfg create mode 100644
>>> meta/cfg/kernel-cache/features/btrfs/btrfs.scc
>>> 
>>> diff --git a/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
>> b/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg
>>> new file mode 100644 index 0000000..605c183 --- /dev/null +++
>>> b/meta/cfg/kernel-cache/features/btrfs/btrfs.cfg @@ -0,0 +1 @@ 
>>> +CONFIG_BTRFS_FS=y diff --git
>>> a/meta/cfg/kernel-cache/features/btrfs/btrfs.scc
>> b/meta/cfg/kernel-cache/features/btrfs/btrfs.scc
>>> new file mode 100644 index 0000000..cf18a2e --- /dev/null +++
>>> b/meta/cfg/kernel-cache/features/btrfs/btrfs.scc @@ -0,0 +1 @@ 
>>> +kconf non-hardware btrfs.cfg


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


  reply	other threads:[~2011-09-09 21:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-06 19:55 [PATCH 0/1] add a btrfs feature in linux-yocto-3.0 nitin.a.kamble
2011-09-06 19:56 ` [PATCH 1/1] btrfs: Add a new kernel feature to enable the btrfs support nitin.a.kamble
2011-09-06 20:30   ` Bruce Ashfield
2011-09-09 16:14     ` Kamble, Nitin A
2011-09-09 21:09       ` Darren Hart [this message]
2011-09-13 20:16     ` Kamble, Nitin A
2011-09-13 20:17       ` Ashfield, Bruce
2011-09-13 21:19         ` Kamble, Nitin A
2011-09-15  4:08         ` 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=4E6A8081.90605@intel.com \
    --to=darren.hart@intel.com \
    --cc=nitin.a.kamble@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.