From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Chang, Rebecca Swee Fun" <rebecca.swee.fun.chang@intel.com>,
OpenEmbedded Core Mailing List
<openembedded-core@lists.openembedded.org>,
"Burton, Ross" <ross.burton@intel.com>
Cc: Internal Core dev Mailing List <core-dev@eclists.intel.com>,
"Eggleton, Paul" <paul.eggleton@intel.com>
Subject: Re: [PATCHv3 0/2] devshell: make sure toolchains are populated in sysroot
Date: Mon, 05 Jun 2017 09:22:50 +0100 [thread overview]
Message-ID: <1496650970.6630.175.camel@linuxfoundation.org> (raw)
In-Reply-To: <50B33AC5ED75F74F991980326F1C438D1F050F18@PGSMSX103.gar.corp.intel.com>
On Mon, 2017-06-05 at 01:15 +0000, Chang, Rebecca Swee Fun wrote:
> Hi all,
>
> May I know is this patch in queue for merging? This fix was planned
> for 2.4M1.
> Thank you very much.
I've queued these in -next, thanks.
Richard
prev parent reply other threads:[~2017-06-05 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 1:42 [PATCHv3 0/2] devshell: make sure toolchains are populated in sysroot rebecca.swee.fun.chang
2017-06-05 1:15 ` Chang, Rebecca Swee Fun
2017-06-05 8:22 ` 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=1496650970.6630.175.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=core-dev@eclists.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@intel.com \
--cc=rebecca.swee.fun.chang@intel.com \
--cc=ross.burton@intel.com \
/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.