All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Glenn Schmottlach <gschmottlach@gmail.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: Trouble modifying defconfig for linux-ti-staging_rt recipe
Date: Wed, 22 Mar 2017 15:50:27 -0400	[thread overview]
Message-ID: <20170322195027.GB29187@edge> (raw)
In-Reply-To: <CAMS2kBErBWJj19WOM+5K=40h22zqypdLxS1N6UfFK=kgva3fUg@mail.gmail.com>

On Wed, Mar 22, 2017 at 03:41:22PM -0400, Glenn Schmottlach wrote:
> >
> > Looks good... Can you try moving your defconfig into "ti33x" folder?
> >
> > recipes-kernel/linux/linux-ti-staging-rt_%.bbappend
> > recipes-kernel/linux/linux-ti-staging-rt/ti33x/defconfig
> >
> 
> You're a genius! ;-)
> 
> I moved the defconfig into a ti33x sub-directory and it appears
> bitbake now uses my defconfig instead of the (default) one. So at
> least now I have two approaches for configuring different kernel
> options: replace the defconfig with my own or use fragments for
> surgical strikes.
> 
> Thanks so much for your help . . .

You are welcome. It's interesting that file overrides are still in play and 
take precedence with bbappends... Need to keep that in mind.

-- 
Denys


      reply	other threads:[~2017-03-22 19:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 15:44 Trouble modifying defconfig for linux-ti-staging_rt recipe Glenn Schmottlach
2017-03-20 15:45 ` Florian Wickert
2017-03-20 15:54 ` Denys Dmytriyenko
2017-03-20 18:14   ` Glenn Schmottlach
2017-03-20 20:15     ` Denys Dmytriyenko
2017-03-20 20:59       ` Glenn Schmottlach
2017-03-20 21:08         ` Denys Dmytriyenko
2017-03-21 11:52           ` Glenn Schmottlach
2017-03-21 17:45             ` Denys Dmytriyenko
2017-03-22 19:41               ` Glenn Schmottlach
2017-03-22 19:50                 ` Denys Dmytriyenko [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=20170322195027.GB29187@edge \
    --to=denys@ti.com \
    --cc=gschmottlach@gmail.com \
    --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.