From: Jeff Layton <jlayton@redhat•com>
To: "J. Bruce Fields" <bfields@fieldses•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
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 14:16:43 -0400 [thread overview]
Message-ID: <20130403141643.1872e17e@tlielax.poochiereds.net> (raw)
In-Reply-To: <20130403180519.GA6044@fieldses.org>
On Wed, 3 Apr 2013 14:05:19 -0400
"J. Bruce Fields" <bfields@fieldses•org> wrote:
> On Wed, Apr 03, 2013 at 07:38:57AM -0400, Jeff Layton wrote:
> > On Wed, 3 Apr 2013 07:33:01 -0400
> > "J. Bruce Fields" <bfields@fieldses•org> wrote:
> >
> > > On Wed, Apr 03, 2013 at 07:10:54AM -0400, Jeff Layton wrote:
> > > > 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.
> > >
> > > Arrgh, sorry--could you remind me which is the new one?
> > >
> >
> > It was the one I sent on 3/19. Those patches (plus a couple more) are
> > also in the current nfsd-3.10 branch of my git tree too, so it may be
> > easiest to just pick them from there.
>
> I hate rewriting that branch, but OK, done: does my for-3.10 look right
> to you now?
>
> (It's still missing some of your latest patches.)
>
> --b.
Yeah, sorry for that... I didn't find the problem with __udivdi3
until after I had asked you to merge the earlier set. Mea culpa...
Latest branch looks good. It would be good to get the later patches in
too, but those are less important than the DRC ones.
Thanks,
--
Jeff Layton <jlayton@redhat•com>
prev parent reply other threads:[~2013-04-03 18:16 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
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 [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=20130403141643.1872e17e@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