All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Ferland <ferlandm@sonatest.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: variable override question
Date: Tue, 25 Jun 2013 17:28:04 -0400	[thread overview]
Message-ID: <874nclc23f.fsf@sonatest.com> (raw)
In-Reply-To: <51C9F9EC.6070305@windriver.com> (Bruce Ashfield's message of "Tue, 25 Jun 2013 16:13:32 -0400")

Bruce Ashfield <bruce.ashfield@windriver.com> writes:

> On 13-06-25 03:59 PM, Marc Ferland wrote:
>> Hi,
>>
>> I have a linux-yocto_3.4.bbappend file in which I try to override the
>> KERNEL_FEATURES variable. I want it to be empty (I don't want the
>> netfilter stuff that's there by default).
>>
>> So I've tried (in my bbappend):
>>
>> KERNEL_FEATURES = ""
>>
>> but somehow the netfilter.scc file still gets merged in.
>>
>> What am I doing wrong?
>
> Nothing. It's an artifact of the _appends that are present
> in the linux-yocto recipe bbappends. You can clear it, but they'll
> still append.
>
> Those config fragments weren't optional when the recipes were
> created, we've since evolved to the point where they are.
>
> I squeezed in a change to linux-yocto_3.8 before the yocto 1.4
> cutoff, and have changed linux-yocto_3.4 to match, and strangely,
> was about to send a consolidated pull request that contains the
> change.
>
> You can either locally make the same change, and clear:
>
>  KERNEL_EXTRA_FEATURES
>
> or wait for my latest update.
>
Nice, exactly what I was looking for!

Thanks,

Marc


      reply	other threads:[~2013-06-25 21:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 19:59 variable override question Marc Ferland
2013-06-25 20:13 ` Bruce Ashfield
2013-06-25 21:28   ` Marc Ferland [this message]

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=874nclc23f.fsf@sonatest.com \
    --to=ferlandm@sonatest.com \
    --cc=bruce.ashfield@windriver.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.