All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for May 7 (argh)
Date: Wed, 07 May 2014 13:52:02 -0700	[thread overview]
Message-ID: <536A9CF2.90906@infradead.org> (raw)
In-Reply-To: <20140507173341.753d8ccf4fe033abd513f98f@canb.auug.org.au>

On 05/07/2014 12:33 AM, Stephen Rothwell wrote:
> Hi all,
> 
> This tree still fails (more than usual) the powerpc allyesconfig build
> and also the celleb_defconfig.
> 
> Changes since 20140506:
> 

I was away for one week.  Did I miss some new instructions about
building linux-next?

I get a thousands of messages like these:

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'



Thanks!
-- 
~Randy

  reply	other threads:[~2014-05-07 20:52 UTC|newest]

Thread overview: 13+ 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  7:33 ` Stephen Rothwell
2014-05-07 20:52 ` Randy Dunlap [this message]
2014-05-07 21:45   ` linux-next: Tree for May 7 (argh) Jim Davis
2014-05-07 22:02     ` Stephen Rothwell
2014-05-07 22:17       ` Jim Davis
2014-05-08  1:10         ` Andi Kleen
2014-05-08 16:54           ` Randy Dunlap
2014-05-08 17:05           ` Jim Davis
2014-05-08 17:08             ` Andi Kleen
2014-05-08 17:40               ` Jim Davis
2014-05-07 21:56   ` Stephen Rothwell
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=536A9CF2.90906@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.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 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.