From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Yocto Project <yocto@yoctoproject.org>,
Darren Hart <dvhart@linux.intel.com>
Subject: Re: linux-yocto_3.0: pull powerpc compile fix for -0s in BOOTFLAGS
Date: Wed, 10 Aug 2011 00:28:28 -0400 [thread overview]
Message-ID: <4E4208EC.7050605@windriver.com> (raw)
In-Reply-To: <DFB04F62-E333-4697-9967-8DBE77F6420B@kernel.crashing.org>
On 11-08-10 12:24 AM, Kumar Gala wrote:
>
> On Aug 9, 2011, at 11:18 PM, Darren Hart wrote:
>
>> Bruce,
>>
>> The following patch is needed for qemuppc and fsl-mpc8315e-rdb (same
>> reasons as before). Can you pull this in from the 2.6.37 yocto tree?
>>
>> commit 5ff609967ffe87c49d534d7861a7e0b150517726
>> Author: Bruce Ashfield<bruce.ashfield@windriver.com>
>> Date: Thu Oct 14 16:38:00 2010 -0400
>>
>> powerpc/boot: remove -Os from BOOTFLAGS
>>
>> Thanks,
>
> Before we do this I have a query about default toolchain? I just posted a patch that should make this NOT needed if we utilize gcc-4.6
>
> So wondering what the feeling was about a fix to kernel tree needed for one version of toolchain and not another?
As long as it fixes one build (the 4.5 one), and doesn't beak other
toolchain versions. I'm typically ok with any patch of that nature.
At the time, this was the fastest thing to do to get the kernel
building with gcc 4.5, but we can absolutely update it with
something newer.
Cheers,
Bruce
>
> - k
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2011-08-10 4:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 4:18 linux-yocto_3.0: pull powerpc compile fix for -0s in BOOTFLAGS Darren Hart
2011-08-10 4:24 ` Kumar Gala
2011-08-10 4:28 ` Bruce Ashfield [this message]
2011-08-10 4:26 ` Bruce Ashfield
2011-08-10 6:21 ` Darren Hart
2011-08-10 13:21 ` Bruce Ashfield
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=4E4208EC.7050605@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=galak@kernel.crashing.org \
--cc=yocto@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.