From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Søren Holm" <sgh@sgh.dk>
Cc: yocto@yoctoproject.org
Subject: Re: defconfig on daisy
Date: Fri, 11 Apr 2014 15:05:56 -0400 [thread overview]
Message-ID: <53483D14.7020807@windriver.com> (raw)
In-Reply-To: <7023738.t8MMlfpnim@koontz>
On 14-04-11 02:43 PM, Søren Holm wrote:
> Hi Bruce
>
> That sounds great. The situation is that I though that that was the case, so I
> also tried adding this to the bbappend.
>
> KERNEL_FEATURES_append = " features/aufs"
>
> But that does not seem to work either. So I guess you are talking about
> somthing else.
I am. There's a missing patch that I typically carry, it actually
links the fs/aufs directory into the build. Without it, the Kconfig
and code isn't processed .. hence why everything is dropped.
I have it merged now, but have to build aufs for all architectures to
make sure nothing broke.
Bruce
>
> Fredag den 11. april 2014 12:51:01 skrev Bruce Ashfield:
>> On 14-04-11 12:15 PM, Søren Holm wrote:
>>> Ok
>>>
>>> Using the *exact* same bbappend file for both 3.10 and 3.14 gives me a
>>> correct -config for 3.10 but not for 3.14. Both 3.10/defconfig and
>>> 3.14/defconfig contains my original defconfig, so it is picked up and
>>> should be taken into account.
>>
>> This is a slightly different problem .. I can see that I managed to
>> drop a patch which links AUFS into the build. Hence why everything
>> is dropped.
>>
>> I'm fixing that right now in 3.14, and will send updates later.
>>
>
next prev parent reply other threads:[~2014-04-11 19:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 21:41 defconfig on daisy Søren Holm
2014-04-11 4:19 ` Bruce Ashfield
2014-04-11 7:39 ` Søren Holm
2014-04-11 13:49 ` Bruce Ashfield
2014-04-11 15:03 ` Søren Holm
2014-04-11 15:05 ` Bruce Ashfield
2014-04-11 15:21 ` Søren Holm
2014-04-11 15:24 ` Bruce Ashfield
2014-04-11 16:15 ` Søren Holm
2014-04-11 16:51 ` Bruce Ashfield
2014-04-11 18:43 ` Søren Holm
2014-04-11 19:05 ` Bruce Ashfield [this message]
2014-04-22 6:13 ` Søren Holm
2014-04-22 8:46 ` Richard Purdie
2014-04-22 17:47 ` Søren Holm
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=53483D14.7020807@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=sgh@sgh.dk \
--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.