From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Bunch of CRC errors in next with arm: move exports to definitions
Date: Fri, 26 Aug 2016 19:53:37 +0100 [thread overview]
Message-ID: <20160826185337.GY5783@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160826184605.4a4u4bxoknmdlgai@atomide.com>
On Fri, Aug 26, 2016 at 11:46:06AM -0700, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [160826 11:20]:
> > * Tony Lindgren <tony@atomide.com> [160822 09:28]:
> > > Hi Al,
> > >
> > > Looks like starting with next-20160818 I'm now getting close to
> > > 800 lines of WARNINGs on ARM with omap2plus_defconfig while doing
> > > make modules:
> > ...
> > > Reverting commit 4dd1837d7589 ("arm: move exports to definitions")
> > > fixes it.
> >
> > And not happening with multi_v7_defconfig for example. Adding Russell
> > to Cc, maybe he already has a fix for this one?
>
> And this issue does not seem to happen with omap2plus_defconfig when
> compiled with:
>
> gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29)
>
> But does happen when compiled with:
>
> gcc version 6.1.1 20160705 (Debian 6.1.1-9)
Hmm, if it's a "bleeding edge gcc" issue, I won't see it anyway, my
cross-compiler is still 4.7.4! Even my ubuntu boxes are only on
4.8.4...
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-08-26 18:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 16:25 Bunch of CRC errors in next with arm: move exports to definitions Tony Lindgren
2016-08-26 18:19 ` Tony Lindgren
2016-08-26 18:46 ` Tony Lindgren
2016-08-26 18:53 ` Russell King - ARM Linux [this message]
2016-08-26 18:51 ` Russell King - ARM Linux
2016-10-18 4:59 ` Sebastian Reichel
2016-10-18 9:13 ` Arnd Bergmann
2016-10-18 9:36 ` Russell King - ARM Linux
2016-10-18 10:00 ` Arnd Bergmann
2016-10-20 13:24 ` 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=20160826185337.GY5783@n2100.arm.linux.org.uk \
--to=linux@armlinux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).