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: Tue, 18 Oct 2016 10:36:28 +0100 [thread overview]
Message-ID: <20161018093628.GE5783@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <6218660.zgecHdOkUb@wuerfel>
On Tue, Oct 18, 2016 at 11:13:31AM +0200, Arnd Bergmann wrote:
> On Tuesday, October 18, 2016 6:59:44 AM CEST Sebastian Reichel wrote:
> > Hi,
> >
> > On Mon, Aug 22, 2016 at 09:25:13AM -0700, Tony Lindgren wrote:
> > > 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:
> > >
> > > Building modules, stage 2.
> > > MODPOST 399 modules
> > > WARNING: "__memzero" [sound/usb/snd-usbmidi-lib.ko] has no CRC!
> > > WARNING: "memset" [sound/usb/snd-usbmidi-lib.ko] has no CRC!
> > > WARNING: "memcpy" [sound/usb/snd-usbmidi-lib.ko] has no CRC!
> > > WARNING: "_set_bit" [sound/usb/snd-usbmidi-lib.ko] has no CRC!
> > > WARNING: "_test_and_set_bit" [sound/usb/snd-usbmidi-lib.ko] has no CRC!
> > > WARNING: "_clear_bit" [sound/usb/snd-usbmidi-lib.ko] has no CRC!
> > > WARNING: "__aeabi_uidivmod" [sound/usb/snd-usb-audio.ko] has no CRC!
> > > WARNING: "_test_and_clear_bit" [sound/usb/snd-usb-audio.ko] has no CRC!
> > > WARNING: "arm_copy_to_user" [sound/usb/snd-usb-audio.ko] has no CRC!
> > > WARNING: "__aeabi_uidiv" [sound/usb/snd-usb-audio.ko] has no CRC!
> > > ...
> > > WARNING: "memset" [crypto/drbg.ko] has no CRC!
> > > WARNING: "memcpy" [crypto/ctr.ko] has no CRC!
> > > WARNING: "memcpy" [crypto/cmac.ko] has no CRC!
> > > WARNING: "__memzero" [crypto/cmac.ko] has no CRC!
> > > WARNING: "memcpy" [crypto/ccm.ko] has no CRC!
> > > WARNING: "__memzero" [crypto/ccm.ko] has no CRC!
> >
> > Any update on this one? I just updated my power-supply next branch
> > to v4.9-rc1 and now get almost 18000 CRC warnings for allmodconfig.
> > (I use arm-linux-gnueabihf-gcc (Debian 6.1.1-9) 6.1.1 20160705)
>
> Nick did a patch to fix this in general, and in powerpc specifically,
> I sent a patch yesterday to fix the ARM specific symbols.
Did you now? You failed to _at least_ copy me on that. This is clearly
about core ARM code and not arm-soc stuff, you should always copy me on
such changes, and if I were Lee Jones, I'd insist that it was merged
through my tree.
--
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-10-18 9:36 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
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 [this message]
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=20161018093628.GE5783@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).