All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hongxu Jia <hongxu.jia@windriver.com>
To: "Eric Bénard" <eric@eukrea.com>
Cc: qingtao.cao@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [danny][PATCH 0/2]fix toolchain relocation issues
Date: Thu, 7 Mar 2013 09:37:16 +0800	[thread overview]
Message-ID: <5137EF4C.4050302@windriver.com> (raw)
In-Reply-To: <20130306211447.27f6b262@e6520eb>

On 03/07/2013 04:14 AM, Eric Bénard wrote:
> Hi Hongxu,
>
> Le Wed, 6 Mar 2013 12:58:45 +0800,
> Hongxu Jia <hongxu.jia@windriver.com> a écrit :
>
>> Rebase to danny.
>>
>> [YOCTO #3984]
>>
>> The following changes since commit e89f812a0af56beda951c1dce6113a61d6db8cda:
>>
>>    bitbake: knotty.py: fix unknown event bb.event.DiskFull (2013-03-04 10:17:20 +0000)
>>
>> are available in the git repository at:
>>
>>    git://git.pokylinux.org/poky-contrib hongxu/fix-toolchain-relocation-danny
>>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/fix-toolchain-relocation-danny
>>
>> Hongxu Jia (2):
>>    perl-nativesdk:fix toolchain relocation issues
>>    populate_sdk_base.bbclass:fix toolchain relocation issues
>>
> while at it, may you please also cherry-pick
> e7a21cd69a326ab7e2d0e410db28f24956f61208
> which is "toolchain-scripts.bbclass: add PYTHONHOME variable to
> environment-setup"
>
> as the problem described in [YOCTO #3839] is also present in danny.
>
> Thanks
> Eric
Ok, I will handle it and resend the patch later.

Thanks,
Hongxu



      reply	other threads:[~2013-03-07  1:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06  4:58 [danny][PATCH 0/2]fix toolchain relocation issues Hongxu Jia
2013-03-06  4:58 ` [danny][PATCH 1/2] perl-nativesdk:fix " Hongxu Jia
2013-03-06  4:58 ` [danny][PATCH 2/2] populate_sdk_base.bbclass:fix " Hongxu Jia
2013-03-06 20:14 ` [danny][PATCH 0/2]fix " Eric Bénard
2013-03-07  1:37   ` Hongxu Jia [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=5137EF4C.4050302@windriver.com \
    --to=hongxu.jia@windriver.com \
    --cc=eric@eukrea.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=qingtao.cao@windriver.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.