All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH] netbase: Fix file search path for 'interfaces'
Date: Wed, 16 Jan 2013 13:10:10 -0500	[thread overview]
Message-ID: <20130116181010.GA19126@denix.org> (raw)
In-Reply-To: <50F6BF5E.3020705@mlbassoc.com>

On Wed, Jan 16, 2013 at 07:55:26AM -0700, Gary Thomas wrote:
> On 2013-01-14 16:31, Denys Dmytriyenko wrote:
> >On Sat, Dec 29, 2012 at 05:36:29AM -0700, Gary Thomas wrote:
> >>This .bbappend file is used to override the 'interfaces' file for
> >>certain targets.  The current version is broken in that it does not
> >>search the correct path(s).  This patch fixes that, as well as marking
> >>the resulting package as target specific.
> >
> >Thanks. There was similar patch earlier, but w/o marking resulting package as
> >machine specific. For that matter, shouldn't the main netbase recipe in
> >oe-core do it instead? As it comes with bunch of qemu-arch-specific interfaces
> >files anyway, and we just add one more for beagleboard...
> >
> 
> Agreed.  When I get two minutes, I'll propose a new patch for meta-ti
> for this as well as one for OE-core.

Actually, there is no need for an explicit PACKAGE_ARCH = MACHINE_ARCH neither 
in bbappend nor in the main recipe in oe-core - bitbake does it automatically 
when it detects machine-overriden files being packaged.

-- 
Denys


  reply	other threads:[~2013-01-16 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-29 12:36 [PATCH] netbase: Fix file search path for 'interfaces' Gary Thomas
2013-01-14 23:31 ` Denys Dmytriyenko
2013-01-16 14:55   ` Gary Thomas
2013-01-16 18:10     ` Denys Dmytriyenko [this message]
2013-01-16 18:25       ` Gary Thomas

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=20130116181010.GA19126@denix.org \
    --to=denys@ti.com \
    --cc=gary@mlbassoc.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.