From: "Eric Bénard" <eric@eukrea.com>
To: Andrei Gherzan <andrei@gherzan.ro>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Andrei Gherzan <andrei.gherzan@windriver.com>
Subject: Re: [meta-fsl-arm][PATCH 1/3] u-boot: Rename recipe to u-boot-fsl
Date: Fri, 14 Dec 2012 15:01:50 +0100 [thread overview]
Message-ID: <20121214150150.1aa8eaf5@eb-e6520> (raw)
In-Reply-To: <CAK18fxEDGrWDa7UBw_iAa-v8EU8W8U-Z=irNLO3j9yMbwH8H=g@mail.gmail.com>
Le Fri, 14 Dec 2012 15:56:11 +0200,
Andrei Gherzan <andrei@gherzan.ro> a écrit :
> On Fri, Dec 14, 2012 at 3:53 PM, Eric Bénard <eric@eukrea.com> wrote:
>
> > Hi Andrei,
> >
> > Le Fri, 14 Dec 2012 13:57:12 +0200,
> > Andrei Gherzan <andrei.gherzan@windriver.com> a écrit :
> >
> > > It's not right to have a recipe named as uboot even if it uses a repo
> > > specific to freescale boards. This would lead to issues while using other
> > > bsp layers in conjunction to meta-fsl-arm where different u-boot versions
> > > but same uboot name are used.
> > >
> > why don't you simply add a COMPATIBLE_MACHINE in the u-boot recipe ?
> >
>
> It's not about our layer. It's about making this work with layers which
> don't have that.
>
that don't have what ?
Eric
next prev parent reply other threads:[~2012-12-14 14:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 11:57 [meta-fsl-arm][PATCH 1/3] u-boot: Rename recipe to u-boot-fsl Andrei Gherzan
2012-12-14 11:57 ` [meta-fsl-arm][PATCH 2/3] u-boot-fsl: This recipe provides u-boot Andrei Gherzan
2012-12-14 11:57 ` [meta-fsl-arm][PATCH 3/3] fsl-default-providers.inc: u-boot recipe was renamed to u-boot-fsl Andrei Gherzan
2012-12-14 12:00 ` [meta-fsl-arm][PATCH 1/3] u-boot: Rename recipe " Andrei Gherzan
2012-12-14 12:36 ` Daiane Angolini
2012-12-14 12:41 ` Otavio Salvador
2012-12-14 12:43 ` Andrei Gherzan
2012-12-14 13:20 ` Daiane Angolini
2012-12-14 13:23 ` Andrei Gherzan
2012-12-14 12:56 ` Daiane Angolini
2012-12-14 12:27 ` Daiane Angolini
2012-12-14 13:53 ` Eric Bénard
2012-12-14 13:56 ` Andrei Gherzan
2012-12-14 14:01 ` Eric Bénard [this message]
2012-12-14 14:04 ` Andrei Gherzan
2012-12-14 14:13 ` Eric Bénard
[not found] ` <CAK18fxF6VYBTZChgrO_n9PGge8tCWngyFPw=6JD+8sTBMPmeTQ@mail.gmail.com>
2012-12-14 14:26 ` Eric Bénard
2012-12-14 15:14 ` Otavio Salvador
2012-12-14 15:30 ` Eric Bénard
2012-12-14 15:33 ` Otavio Salvador
2012-12-14 16:50 ` Daiane Angolini
2012-12-14 16:53 ` Otavio Salvador
2012-12-14 17:29 ` Andrei Gherzan
2012-12-14 17:52 ` Otavio Salvador
2012-12-14 17:58 ` Eric Bénard
2012-12-14 18:12 ` Otavio Salvador
2012-12-14 18:22 ` Eric Bénard
[not found] ` <CA+jg_OWZpR7iazC=anVXbFFbzm8jV5O-f1ZwOoTuC3a3j-kzTA@mail.gmail.com>
2012-12-14 23:08 ` Daiane Angolini
2012-12-14 23:11 ` Andrei Gherzan
2012-12-14 23:20 ` Eric Bénard
2012-12-15 16:04 ` Otavio Salvador
2012-12-15 18:18 ` Eric Bénard
2012-12-15 18:33 ` Otavio Salvador
2012-12-15 20:43 ` Andrei Gherzan
2012-12-16 14:30 ` Daiane Angolini
2012-12-16 17:06 ` Otavio Salvador
2012-12-19 19:35 ` McClintock Matthew-B29882
2012-12-19 19:40 ` Otavio Salvador
2012-12-19 19:46 ` McClintock Matthew-B29882
2012-12-19 19:54 ` Otavio Salvador
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=20121214150150.1aa8eaf5@eb-e6520 \
--to=eric@eukrea.com \
--cc=andrei.gherzan@windriver.com \
--cc=andrei@gherzan.ro \
--cc=meta-freescale@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.