From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Randy Witt <randy.e.witt@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] mtools uninative fix
Date: Sat, 05 Mar 2016 09:43:25 +0000 [thread overview]
Message-ID: <1457171005.2804.76.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1457154293.git.randy.e.witt@linux.intel.com>
On Fri, 2016-03-04 at 21:06 -0800, Randy Witt wrote:
> These patchset is against master next to fix previous uninative
> patches. They
> most likely will not apply cleanly to master.
Thanks for this. There were a couple of issues, I worried what would
happen in the non-uninative case since GCONV_PATH is set
unconditionally. This also didn't update both mtools recipes.
I'm testing a different version of this idea which I've just sent out
but its based on this idea.
Cheers,
Richard
prev parent reply other threads:[~2016-03-05 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 5:06 [PATCH 0/2] mtools uninative fix Randy Witt
2016-03-05 5:06 ` [PATCH 1/2] uninative.bbclass: Set UNINATIVE_LIBDIR if uninative is enabled Randy Witt
2016-03-05 5:06 ` [PATCH 2/2] mtools: Make sure mcopy works when using uninative Randy Witt
2016-03-05 9:43 ` 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=1457171005.2804.76.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.e.witt@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox