All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: meta-ti@yoctoproject.org
Subject: Re: Turning off kernel config option
Date: Tue, 07 Aug 2012 11:41:35 -0400	[thread overview]
Message-ID: <5021372F.2080705@balister.org> (raw)
In-Reply-To: <20120807153806.GC8716@edge>

On 08/07/2012 11:38 AM, Denys Dmytriyenko wrote:
>
>> Or just increment PR as you're supposed to, it's an output change after all.
>> No need to check anything if you do it properly :)

And if you are like me, it would take about 10 PR increments just to get 
the change working properly. Then you would ask me what I changed in 
those PR's :)

Philip

>
> Well, but then you are staring to change the recipe, which might be overkill
> for a simple defconfig change you want to test. If you go that route, you may
> want to create your own custom layer with the modified defconfig overlayed on
> top of meta-ti and a simple .bbappend with PRINC. That way your changes will
> be detached from meta-ti and you won't need to merge the recipe changes every
> time meta-ti updates... Although, there's no way to bbappend the defconfig
> itself - that's where config fragments come to play.
>


  reply	other threads:[~2012-08-07 15:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07  9:02 Turning off kernel config option Jack Mitchell
2012-08-07 15:03 ` Khem Raj
2012-08-07 15:30 ` Denys Dmytriyenko
2012-08-07 15:32   ` Koen Kooi
2012-08-07 15:38     ` Denys Dmytriyenko
2012-08-07 15:41       ` Philip Balister [this message]
2012-08-07 15:44       ` Richard Purdie
2012-08-07 15:53         ` Denys Dmytriyenko
2012-08-07 16:36           ` Jack Mitchell
2012-08-07 17:41             ` Koen Kooi
2012-08-08  8:51               ` Jack Mitchell

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=5021372F.2080705@balister.org \
    --to=philip@balister.org \
    --cc=koen@dominion.thruhere.net \
    --cc=meta-ti@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.