From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] slang: change char type to signed char in macros
Date: Tue, 31 Jul 2012 12:10:57 +0100 [thread overview]
Message-ID: <1343733057.9526.7.camel@ted> (raw)
In-Reply-To: <1343719800-2203-1-git-send-email-rongqing.li@windriver.com>
On Tue, 2012-07-31 at 15:30 +0800, rongqing.li@windriver.com wrote:
> From: Roy.Li <rongqing.li@windriver.com>
>
> [YOCTO 2726]
>
> The patch of converting char type to signed char is only applied to arm,
> in fact it should be applied to powerpc too since powerpc has the same
> assumption for char type. To x86 and mips, this patch has not impact.
>
> Signed-off-by: Roy.Li <rongqing.li@windriver.com>
> ---
> meta/recipes-extended/slang/slang_2.2.4.bb | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
Merged to master, thanks.
Richard
next prev parent reply other threads:[~2012-07-31 11:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 7:30 [PATCH v2] slang: change char type to signed char in macros rongqing.li
2012-07-31 11:10 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-18 2:02 rongqing.li
2012-07-18 2:09 ` Rongqing Li
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=1343733057.9526.7.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