From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2][PULL] multilib: fix multiple (r)provider issue when parsing
Date: Tue, 13 Sep 2011 17:08:45 +0100 [thread overview]
Message-ID: <1315930134.13526.0.camel@ted> (raw)
In-Reply-To: <cover.1315914682.git.dongxiao.xu@intel.com>
On Tue, 2011-09-13 at 19:52 +0800, Dongxiao Xu wrote:
> Dongxiao Xu (2):
> base.bbclass: do not expand PREFERRED_PROVIDER for kernel recipe
> multilib: Remove recipe from multilib.conf that inherits allarch
>
> meta/classes/base.bbclass | 4 +++-
> meta/classes/multilib_global.bbclass | 4 ++++
> meta/conf/multilib.conf | 2 --
> 3 files changed, 7 insertions(+), 3 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-09-13 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 11:52 [PATCH 0/2][PULL] multilib: fix multiple (r)provider issue when parsing Dongxiao Xu
2011-09-13 11:52 ` [PATCH 1/2] base.bbclass: do not expand PREFERRED_PROVIDER for kernel recipe Dongxiao Xu
2011-09-13 11:52 ` [PATCH 2/2] multilib: Remove recipe from multilib.conf that inherits allarch Dongxiao Xu
2011-09-13 16:08 ` 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=1315930134.13526.0.camel@ted \
--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