From: Sage Weil <sage@inktank.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
ceph-devel@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 27 (ceph)
Date: Tue, 27 Aug 2013 12:29:40 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1308271229230.24783@cobra.newdream.net> (raw)
In-Reply-To: <521CF7D6.5090807@infradead.org>
On Tue, 27 Aug 2013, Randy Dunlap wrote:
> On 08/27/13 03:30, Stephen Rothwell wrote:
> > Hi all,
> >
> > I should know better than to take time off around -rc7 :-)
> >
> > Changes since 20130822:
> >
>
> on i386:
>
> fs/built-in.o: In function `ceph_fallocate':
> file.c:(.text+0x20b171): undefined reference to `__divdi3'
I've fixed this up in the ceph tree.
Thanks!
sage
prev parent reply other threads:[~2013-08-27 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 10:30 linux-next: Tree for Aug 27 Stephen Rothwell
2013-08-27 19:02 ` linux-next: Tree for Aug 27 (ceph) Randy Dunlap
2013-08-27 19:29 ` Sage Weil [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=alpine.DEB.2.00.1308271229230.24783@cobra.newdream.net \
--to=sage@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--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).