From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH 4/4] site/powerpc*-linux: refactor needed options that are common
Date: Fri, 22 Jul 2011 12:00:36 +0100 [thread overview]
Message-ID: <1311332436.2344.136.camel@rex> (raw)
In-Reply-To: <4E28BF59.20907@mentor.com>
On Thu, 2011-07-21 at 17:07 -0700, Tom Rini wrote:
> On 07/21/2011 03:30 PM, Kumar Gala wrote:
> > Pulled common options that are needed for powerpc64-linux to build
> > out of powerpc32-linux and put them into powerpc-linux.
> >
> > Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
>
> NAK. Almost all of the stuff going into powerpc-linux really belongs in
> common-linux or common-glibc. Some other tasks held me up here but I
> plan to post the series moving these bits over and dropping them from
> the arch files tomorrow. Rest of the series looks good tho
Sorry, my email reading order wasn't good here and I missed this
comment. I wanted to get the series in since I know this and the stuff
Tom is looking at will likely conflict a bit. Kumar's work improves the
situation so I've merged it. Obviously there is still other improvements
we can have.
Cheers,
Richard
prev parent reply other threads:[~2011-07-22 11:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 22:30 [RFC][PATCH 1/4] site/powerpc: Pull all powerpc config options into powerpc32-linux Kumar Gala
2011-07-21 22:30 ` [RFC][PATCH 2/4] site/powerpc32-linux: Update with ac_cv_sizeof_* from eglibc Kumar Gala
2011-07-21 22:30 ` [RFC][PATCH 3/4] site/powerpc64-linux: Start initial site config Kumar Gala
2011-07-21 22:30 ` [RFC][PATCH 4/4] site/powerpc*-linux: refactor needed options that are common Kumar Gala
2011-07-22 0:07 ` Tom Rini
2011-07-22 11:00 ` Richard Purdie [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=1311332436.2344.136.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox