From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: linux-next: Tree for Aug 13 (xfs)
Date: Tue, 13 Aug 2013 09:59:51 -0700 [thread overview]
Message-ID: <520A6607.7060002@infradead.org> (raw)
In-Reply-To: <20130813182832.16d18ef3dbc267c1a229bcd6@canb.auug.org.au>
On 08/13/13 01:28, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130812:
>
on i386:
fs/built-in.o: In function `xfs_log_calc_minimum_size':
(.text+0x1797a9): undefined reference to `__udivdi3'
--
~Randy
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: linux-next: Tree for Aug 13 (xfs)
Date: Tue, 13 Aug 2013 09:59:51 -0700 [thread overview]
Message-ID: <520A6607.7060002@infradead.org> (raw)
In-Reply-To: <20130813182832.16d18ef3dbc267c1a229bcd6@canb.auug.org.au>
On 08/13/13 01:28, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20130812:
>
on i386:
fs/built-in.o: In function `xfs_log_calc_minimum_size':
(.text+0x1797a9): undefined reference to `__udivdi3'
--
~Randy
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-08-13 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 8:28 linux-next: Tree for Aug 13 Stephen Rothwell
2013-08-13 8:28 ` Stephen Rothwell
2013-08-13 16:59 ` Randy Dunlap [this message]
2013-08-13 16:59 ` linux-next: Tree for Aug 13 (xfs) Randy Dunlap
2013-08-13 18:34 ` Eric Sandeen
2013-08-13 18:34 ` Eric Sandeen
2013-08-13 17:28 ` linux-next: Tree for Aug 13 (acpi/apei/hest.c) Randy Dunlap
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=520A6607.7060002@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.