public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (md tree related)
Date: Mon, 23 Apr 2012 10:18:02 +1000	[thread overview]
Message-ID: <20120423101802.45d59ffc@notabene.brown> (raw)
In-Reply-To: <20120420153448.2257c33126add9118757791a@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]

On Fri, 20 Apr 2012 15:34:48 +1000 Stephen Rothwell <sfr@canb.auug.org.au>
wrote:

> Hi Neil,
> 
> After merging the final tree, today's linux-next build (i386 defconfig)
> failed like this:
> 
> drivers/built-in.o: In function `bitmap_resize':
> (.text+0x202b76): undefined reference to `__udivdi3'
> drivers/built-in.o: In function `bitmap_resize':
> (.text+0x202bac): undefined reference to `__udivdi3'
> 
> Caused by commit 6c5cb1922cca ("md/bitmap: add bitmap_resize function to
> allow bitmap resizing").
> 
> I also get these warnings:
> 
> drivers/md/bitmap.c: In function 'bitmap_resize':
> drivers/md/bitmap.c:1878:11: warning: comparison of distinct pointer types lacks a cast [enabled by default]
> drivers/md/bitmap.c:1887:11: warning: passing argument 3 of 'bitmap_get_counter' from incompatible pointer type [enabled by default]
> drivers/md/bitmap.c:1225:26: note: expected 'sector_t *' but argument is of type 'long int *'
> drivers/md/bitmap.c:1892:12: warning: passing argument 3 of 'bitmap_get_counter' from incompatible pointer type [enabled by default]
> drivers/md/bitmap.c:1225:26: note: expected 'sector_t *' but argument is of type 'long int *'
> drivers/md/bitmap.c:1920:8: warning: passing argument 3 of 'bitmap_get_counter' from incompatible pointer type [enabled by default]
> drivers/md/bitmap.c:1225:26: note: expected 'sector_t *' but argument is of type 'long int *'
> 
> I applied the patch below for the link failure, but the above warnings
> should be addressed as well.

Thanks Stephen.  I've fixed all that up now - and done a test 32-bit
compile :-)

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

      reply	other threads:[~2012-04-23  0:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-20  5:34 linux-next: build failure after merge of the final tree (md tree related) Stephen Rothwell
2012-04-23  0:18 ` NeilBrown [this message]

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=20120423101802.45d59ffc@notabene.brown \
    --to=neilb@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox