From: Stefano Babic <sbabic@denx.de>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
Stefano Babic <sbabic@denx.de>
Cc: marex@denx.de, koen@dominion.thruhere.net,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] ICU: libicudata corrupt on big endian systems
Date: Wed, 17 Jun 2015 19:37:27 +0200 [thread overview]
Message-ID: <5581B057.9050602@denx.de> (raw)
In-Reply-To: <4769027.txEDJ0YG4l@peggleto-mobl.ger.corp.intel.com>
Hi Paul,
On 17/06/2015 19:28, Paul Eggleton wrote:
>> @@ -0,0 +1,35 @@
>> +From 1878e1bfcd116dd3ed9519dd891bf18f860072b7 Mon Sep 17 00:00:00 2001
>> +From: Stefano Babic <sbabic@denx.de>
>> +Date: Thu, 4 Jun 2015 17:53:30 +0200
>> +Subject: [PATCH] target
>
>
> This needs a proper patch comment explaining what it's supposed to do and
> Upstream-Status (probably "Inappropriate" here I guess).
Sure, I'll do
>> +SRC_URI_append_class-native = "${@base_conditional('TUNE_ARCH', 'powerpc',
>> 'file://native_big_endian.patch', '', d)}"
>
> It doesn't change the behaviour here, but it's good practice to ensure that
> there is at least a space between any previous item and the item you are
> appending - so I would recommend including a leading space either before
> file:// or before the ${@ (or you could follow the SRC_URI_append_class-target
> example on the next line).
Thanks, I'll fix it in V2.
Regards,
Stefano
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================
next prev parent reply other threads:[~2015-06-17 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 13:15 [PATCH] ICU: libicudata corrupt on big endian systems Stefano Babic
2015-06-17 17:28 ` Paul Eggleton
2015-06-17 17:37 ` Stefano Babic [this message]
2015-06-17 18:37 ` Richard Purdie
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=5581B057.9050602@denx.de \
--to=sbabic@denx.de \
--cc=koen@dominion.thruhere.net \
--cc=marex@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@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