From: Steven Whitehouse <swhiteho@redhat.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
cluster-devel@redhat.com
Subject: Re: linux-next: Tree for July 20 (gfs2)
Date: Fri, 20 Jul 2012 19:42:09 +0100 [thread overview]
Message-ID: <1342809729.2742.18.camel@menhir> (raw)
In-Reply-To: <5009823B.2010700@xenotime.net>
Hi,
On Fri, 2012-07-20 at 09:07 -0700, Randy Dunlap wrote:
> On 07/19/2012 10:13 PM, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20120719:
> >
>
>
>
>
> on i386 (modular):
>
> ERROR: "__divdi3" [fs/gfs2/gfs2.ko] undefined!
>
> or builtin:
>
> fs/built-in.o: In function `gfs2_fallocate':
> file.c:(.text+0x232086): undefined reference to `__divdi3'
>
Bob has sent me a patch to fix this, and I've just pushed it to the GFS2
-nmw git tree. Thanks for letting us know,
Steve.
prev parent reply other threads:[~2012-07-20 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 5:13 linux-next: Tree for July 20 Stephen Rothwell
2012-07-20 16:07 ` linux-next: Tree for July 20 (gfs2) Randy Dunlap
2012-07-20 18:42 ` Steven Whitehouse [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=1342809729.2742.18.camel@menhir \
--to=swhiteho@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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).