From: Jeff Layton <jlayton@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: "J. Bruce Fields" <bfields@fieldses•org>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (nfsd tree related)
Date: Wed, 3 Apr 2013 07:10:54 -0400 [thread overview]
Message-ID: <20130403071054.45a02a88@tlielax.poochiereds.net> (raw)
In-Reply-To: <20130403174219.0786d27109633a30d89b38bf@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
On Wed, 3 Apr 2013 17:42:19 +1100
Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (arm defconfig)
> failed like this:
>
> fs/built-in.o: In function `nfsd_reply_cache_stats_show':
> super.c:(.text+0x87308): undefined reference to `__udivdi3'
>
> Probably caused by commit 187da2f90879 ("nfsd: keep track of the max and
> average time to search the cache") which adds a divide by u64
> (num_searches).
>
> I have reverted that commit and the following one for today.
Thanks, known problem...
Looks like Bruce's tree has an older version of that patch series. I
think we just need to get him to drop that one and merge the new one.
--
Jeff Layton <jlayton@redhat•com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-03 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 6:42 linux-next: build failure after merge of the final tree (nfsd tree related) Stephen Rothwell
2013-04-03 11:10 ` Jeff Layton [this message]
2013-04-03 11:33 ` J. Bruce Fields
2013-04-03 11:38 ` Jeff Layton
2013-04-03 18:05 ` J. Bruce Fields
2013-04-03 18:16 ` Jeff Layton
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=20130403071054.45a02a88@tlielax.poochiereds.net \
--to=jlayton@redhat$(echo .)com \
--cc=bfields@fieldses$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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