linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Mark Fasheh <mfasheh@suse.com>, Joel Becker <jlbec@evilplan.org>,
	linux-next@vger.kernel.org
Subject: Re: linux-next: Tree for May 27 (ocfs2)
Date: Fri, 27 May 2011 11:21:09 -0700	[thread overview]
Message-ID: <20110527112109.78501105.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110527093043.0840ac30.randy.dunlap@oracle.com>

On Fri, 27 May 2011 09:30:43 -0700 Randy Dunlap wrote:

> On Fri, 27 May 2011 15:52:31 +1000 Stephen Rothwell wrote:
> 
> > Hi all,
> > 
> > Changes since 20110526:
> 
> ocfs2 on i386 has build errors:
> 
> ERROR: "__udivdi3" [fs/ocfs2/ocfs2.ko] undefined!
> ERROR: "__umoddi3" [fs/ocfs2/ocfs2.ko] undefined!
> 
> or when builtin:
> 
> fs/built-in.o: In function `ocfs2_find_victim_alloc_group.clone.0':
> move_extents.c:(.text+0x1fb01a): undefined reference to `__udivdi3'
> fs/built-in.o: In function `ocfs2_validate_and_adjust_move_goal':
> move_extents.c:(.text+0x1fb12e): undefined reference to `__umoddi3'
> move_extents.c:(.text+0x1fb15a): undefined reference to `__udivdi3'
> fs/built-in.o: In function `ocfs2_find_victim_alloc_group.clone.0':
> move_extents.c:(.text+0x1fb01a): undefined reference to `__udivdi3'
> fs/built-in.o: In function `ocfs2_validate_and_adjust_move_goal':
> move_extents.c:(.text+0x1fb12e): undefined reference to `__umoddi3'
> move_extents.c:(.text+0x1fb15a): undefined reference to `__udivdi3'
> fs/built-in.o: In function `ocfs2_find_victim_alloc_group.clone.0':
> move_extents.c:(.text+0x1fb01a): undefined reference to `__udivdi3'
> fs/built-in.o: In function `ocfs2_validate_and_adjust_move_goal':
> move_extents.c:(.text+0x1fb12e): undefined reference to `__umoddi3'
> move_extents.c:(.text+0x1fb15a): undefined reference to `__udivdi3'

Fixed by just-merged mainline commit:

Gitweb:     http://git.kernel.org/linus/6aea6f5068cb86e89a6ac243c3fc131045b6563a
Commit:     6aea6f5068cb86e89a6ac243c3fc131045b6563a
Parent:     dda54e76d7dba0532ebdd72e0b4f492a03f83225
Author:     Tristan Ye <tristan.ye@oracle.com>
AuthorDate: Fri May 27 15:19:56 2011 +0800
Committer:  Tristan Ye <tristan.ye@oracle.com>
CommitDate: Fri May 27 14:52:53 2011 +0800

    Ocfs2/move_extents: Avoid doing division in extent moving.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      reply	other threads:[~2011-05-27 18:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27  5:52 linux-next: Tree for May 27 Stephen Rothwell
2011-05-27 16:30 ` linux-next: Tree for May 27 (ocfs2) Randy Dunlap
2011-05-27 18:21   ` Randy Dunlap [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=20110527112109.78501105.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=jlbec@evilplan.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mfasheh@suse.com \
    --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;
as well as URLs for NNTP newsgroup(s).