From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: linux-next: Tree for May 7 (argh)
Date: Thu, 8 May 2014 07:56:06 +1000 [thread overview]
Message-ID: <20140508075606.fd453d43546aef01b87e3ad1@canb.auug.org.au> (raw)
In-Reply-To: <536A9CF2.90906@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1158 bytes --]
Hi Randy,
On Wed, 07 May 2014 13:52:02 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> I was away for one week. Did I miss some new instructions about
> building linux-next?
Nothing that I know of.
>
> I get a thousands of messages like these:
What config? What arch? Did you just do "make oldconfig"?
> WARNING: "system_wq" [drivers/misc/bh1770glc.ko] has no CRC!
> WARNING: "__wake_up" [drivers/misc/bh1770glc.ko] has no CRC!
> WARNING: "sysfs_notify" [drivers/misc/bh1770glc.ko] has no CRC!
> WARNING: "kfree" [drivers/misc/bh1770glc.ko] has no CRC!
>
> Also there hundreds of messages like these:
>
> ps2mult.c:(.exit.text+0x8f): multiple definition of `cleanup_module'
> ps2mult.c:(.init.text+0xbc8): multiple definition of `init_module'
> ipack.c:(.exit.text+0x0): multiple definition of `cleanup_module'
> ipack.c:(.init.text+0x0): multiple definition of `init_module'
> mcb-core.c:(.text+0x40d): multiple definition of `cleanup_module'
> mcb-core.c:(.text+0x3fb): multiple definition of `init_module'
cc'ing Rusty just in case ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-07 21:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 7:33 linux-next: Tree for May 7 Stephen Rothwell
2014-05-07 20:52 ` linux-next: Tree for May 7 (argh) Randy Dunlap
2014-05-07 21:56 ` Stephen Rothwell [this message]
2014-05-07 22:31 ` Randy Dunlap
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=20140508075606.fd453d43546aef01b87e3ad1@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rusty@rustcorp.com.au \
/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).