From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
Ohad Ben-Cohen <ohad@wizery.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: Latest OMAP4 build errors
Date: Wed, 7 Mar 2012 19:34:40 -0800 [thread overview]
Message-ID: <20120308033439.GR12083@atomide.com> (raw)
In-Reply-To: <20120307234308.GA20364@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [120307 15:11]:
> On Wed, Mar 07, 2012 at 02:44:59PM -0800, Tony Lindgren wrote:
> > OK thanks, will do that next time if there's something urgent.
> >
> > I'll send a pull request shortly for fixes-non-critical-part2 that
> > should sort out the remaining issues.
>
> FYI, I've just updated the build tree with what's in arm-soc (as of
> a couple of minutes ago), which contained a bunch of OMAP updates, so
> I'm hopeful that tomorrows results should show an improvement.
>
> It'll start its run in about 2h20.
Looks like there one new section warning with omap_hsmmc_init_one
depending on the compiler. I'll post a fix for that.
Not seeing that with codesourcery/linaro compilers, but seeing
with the emdebian gcc 4.3.5.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Latest OMAP4 build errors
Date: Wed, 7 Mar 2012 19:34:40 -0800 [thread overview]
Message-ID: <20120308033439.GR12083@atomide.com> (raw)
In-Reply-To: <20120307234308.GA20364@n2100.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [120307 15:11]:
> On Wed, Mar 07, 2012 at 02:44:59PM -0800, Tony Lindgren wrote:
> > OK thanks, will do that next time if there's something urgent.
> >
> > I'll send a pull request shortly for fixes-non-critical-part2 that
> > should sort out the remaining issues.
>
> FYI, I've just updated the build tree with what's in arm-soc (as of
> a couple of minutes ago), which contained a bunch of OMAP updates, so
> I'm hopeful that tomorrows results should show an improvement.
>
> It'll start its run in about 2h20.
Looks like there one new section warning with omap_hsmmc_init_one
depending on the compiler. I'll post a fix for that.
Not seeing that with codesourcery/linaro compilers, but seeing
with the emdebian gcc 4.3.5.
Regards,
Tony
next prev parent reply other threads:[~2012-03-08 3:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 9:02 Latest OMAP4 build errors Russell King - ARM Linux
2012-02-28 9:51 ` Ohad Ben-Cohen
2012-02-28 10:01 ` Arnd Bergmann
2012-02-28 10:11 ` Ohad Ben-Cohen
2012-03-06 16:55 ` Russell King - ARM Linux
2012-03-06 17:01 ` Arnd Bergmann
2012-03-06 17:06 ` Ohad Ben-Cohen
2012-03-07 10:06 ` Russell King - ARM Linux
2012-03-07 17:10 ` Tony Lindgren
2012-03-07 17:10 ` Tony Lindgren
2012-03-07 22:18 ` Olof Johansson
2012-03-07 22:18 ` Olof Johansson
2012-03-07 22:44 ` Tony Lindgren
2012-03-07 22:44 ` Tony Lindgren
2012-03-07 23:43 ` Russell King - ARM Linux
2012-03-07 23:43 ` Russell King - ARM Linux
2012-03-08 3:34 ` Tony Lindgren [this message]
2012-03-08 3:34 ` Tony Lindgren
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=20120308033439.GR12083@atomide.com \
--to=tony@atomide.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ohad@wizery.com \
--cc=olof@lixom.net \
/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.