From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: the oe-core layer <openembedded-core@lists.openembedded.org>, Patches
Subject: Re: [PATCH] soc-family: fix SOC_FAMILY override order
Date: Tue, 12 Mar 2013 06:19:37 +0000 [thread overview]
Message-ID: <1363069177.9859.1.camel@ted> (raw)
In-Reply-To: <CAP9ODKog6e+3BbDT+pLy1a8GsEuKtyZmuuoHGoc3tOX20OvLpg@mail.gmail.com>
On Mon, 2013-03-11 at 13:24 -0300, Otavio Salvador wrote:
> On Mon, Mar 11, 2013 at 11:49 AM, Maupin, Chase <chase.maupin@ti.com> wrote:
> >> On Fri, Mar 8, 2013 at 7:16 PM, Maupin, Chase
> >> We can have more generic to more specific combinations.
> >>
> >> > Or are you trying to build something like omap3->am35xx->am3517
> >> where you can use omap3 as a more generic setting but still use
> >> am35xx for a slightly more restrictive group that is still
> >> grouping like parts, and finally you use am3517 for the exact
> >> part?
> >>
> >> Exactly so we avoid duplication stuff to boards or SoCs. Another
> >> example of use: imx -> mx6q -> mx6.
> >
> > I see. This could be of some use and I'll play with it. This
> should not be required though for this patch since right now I want to
> fix the order issue. Any objection to the patch as is?
>
> No; not really. I just wanted to ask if you could look at it as well
> so we can have it working. It does make things much easier for all us.
As pointed out this already merged.
I'd also point out that you can use MACHINEOVERRIDES directly to specify
additional machine overrides so I'm not sure there is much extra
complexity here that is really needed.
Cheers,
Richard
next prev parent reply other threads:[~2013-03-12 6:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 17:51 [PATCH] soc-family: fix SOC_FAMILY override order Chase Maupin
2013-03-08 18:52 ` Otavio Salvador
2013-03-08 20:06 ` Denys Dmytriyenko
2013-03-08 20:27 ` Otavio Salvador
2013-03-08 22:16 ` Maupin, Chase
2013-03-09 12:10 ` Otavio Salvador
2013-03-11 14:49 ` Maupin, Chase
2013-03-11 16:24 ` Otavio Salvador
2013-03-11 18:03 ` Maupin, Chase
2013-03-11 18:52 ` Denys Dmytriyenko
2013-03-11 19:09 ` Otavio Salvador
2013-03-12 6:19 ` Richard Purdie [this message]
2013-03-12 12:38 ` Otavio Salvador
2013-03-11 20:45 ` Denys Dmytriyenko
2013-03-12 12:06 ` Maupin, Chase
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=1363069177.9859.1.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.