From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Koen Kooi <koen.kooi@linaro.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libpng 1.6.13: fix build for aarch64
Date: Mon, 03 Nov 2014 12:10:27 +0000 [thread overview]
Message-ID: <1415016627.5111.9.camel@ted> (raw)
In-Reply-To: <07F08083-4EDE-4CC7-AAA7-53019C7978C0@dominion.thruhere.net>
On Mon, 2014-11-03 at 13:06 +0100, Koen Kooi wrote:
> > Op 3 nov. 2014, om 12:30 heeft Burton, Ross <ross.burton@intel.com> het volgende geschreven:
> >
> >
> > On 3 November 2014 11:27, Koen Kooi <koen@dominion.thruhere.net> wrote:
> > > Last night I was looking at my "post-1.7" tag and the number of aarch64 patches there. Kai, did you continue work on that staging branch for all of the aarch64 patches that were being posted?
> >
> > What does that have to do with this patch?
> >
> > Kai was collecting patches that were sent to oe-core, and this may have been one of them.
>
> Is this some new requirement for OE-core patches?
Its someone being helpful and trying to consolidate a topic branch and
test things before it gets merged.
So its not a new requirement but it is helpful and appreciated.
Cheers,
Richard
next prev parent reply other threads:[~2014-11-03 12:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 12:12 [PATCH] libpng 1.6.13: fix build for aarch64 Koen Kooi
2014-11-03 9:57 ` Koen Kooi
2014-11-03 10:25 ` Burton, Ross
2014-11-03 11:27 ` Koen Kooi
2014-11-03 11:30 ` Burton, Ross
2014-11-03 12:06 ` Koen Kooi
2014-11-03 12:10 ` Richard Purdie [this message]
2014-11-03 15:24 ` Koen Kooi
2014-11-03 16:08 ` Burton, Ross
2014-11-03 17:13 ` Koen Kooi
2014-11-03 17:33 ` Burton, Ross
2014-11-03 16:08 ` Richard Purdie
2014-11-03 17:38 ` Mark Hatle
2014-11-03 17:44 ` Burton, Ross
2014-11-04 2:30 ` Kang Kai
2014-12-12 8:42 ` Koen Kooi
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=1415016627.5111.9.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen.kooi@linaro.org \
--cc=koen@dominion.thruhere.net \
--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