From: Saul Wold <saul.wold@intel.com>
To: Jessica Zhang <jessica.zhang@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/1] Remove sanity check for i686
Date: Tue, 18 Jan 2011 14:44:00 -0800 [thread overview]
Message-ID: <4D3617B0.3020009@intel.com> (raw)
In-Reply-To: <cover.1295288961.git.jessica.zhang@intel.com>
On 01/17/2011 10:29 AM, Jessica Zhang wrote:
> I've tested against a newly built toolchain with host as i686 and target as i586 and used the toolchain cross compile cvs(c) and suduku(c++) applications and ran them on the target without issues.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: jzhang/bitbake_i686
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=jzhang/bitbake_i686
>
> Thanks,
> Jessica Zhang<jessica.zhang@intel.com>
> ---
>
>
> Jessica Zhang (1):
> remove sanity check for SDK_ARCH=i686 due to recent fixes in cross
> toolchain areas, etc. the old issue no longer exists
>
Jessica:
Can you re-submit this with a more correct subject line, the format is
typically:
<recipe/bbclass>: short synopsis
[Blank Line]
Longer Description of fix if needed
Signed-off-by: ...
For example this one might be:
sanity.bbclass: remove SDK_ARCH Check
remove sanity check for SDK_ARCH=i686 due to recent fixes in cross
toolchain areas, etc. the old issue no longer exists
Thanks
Sau!
> meta/classes/sanity.bbclass | 3 ---
> 1 files changed, 0 insertions(+), 3 deletions(-)
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
prev parent reply other threads:[~2011-01-18 22:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 18:29 [PATCH 0/1] Remove sanity check for i686 Jessica Zhang
2011-01-17 18:25 ` [PATCH 1/1] remove sanity check for SDK_ARCH=i686 due to recent fixes in cross toolchain areas, etc. the old issue no longer exists Jessica Zhang
2011-01-18 22:44 ` Saul Wold [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=4D3617B0.3020009@intel.com \
--to=saul.wold@intel.com \
--cc=jessica.zhang@intel.com \
--cc=poky@yoctoproject.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 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.