linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sage Weil <sage@newdream.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Greg Farnum <gregf@hq.newdream.net>
Subject: Re: linux-next: build failure after merge of the ceph tree
Date: Sun, 19 Sep 2010 19:53:08 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.1009191952540.7498@cobra.newdream.net> (raw)
In-Reply-To: <20100920114136.33d75323.sfr@canb.auug.org.au>

On Mon, 20 Sep 2010, Stephen Rothwell wrote:
> Hi Sage,
> 
> After merging the vfs tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> net/ceph/pagelist.c: In function 'ceph_pagelist_truncate':
> net/ceph/pagelist.c:136: error: implicit declaration of function 'pagelist_unmap_tail'
> 
> Caused by commit d73f8eefea20406cba00b80a65747844df120559 ("ceph: add pagelist_reserve, pagelist_truncate, pagelist_set_cursor").
> 
> I have used the version of the ceph tree from next-20100917 for today.

Fixed.  Thanks!

sage

  reply	other threads:[~2010-09-20  2:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-20  1:41 linux-next: build failure after merge of the ceph tree Stephen Rothwell
2010-09-20  2:53 ` Sage Weil [this message]
2010-11-16 23:43 Stephen Rothwell
2010-11-17  0:02 ` Sage Weil
2012-03-21  1:40 Stephen Rothwell
2012-03-21  4:24 ` Alex Elder
2013-09-26  1:15 Stephen Rothwell
2013-09-26  1:20 ` majianpeng
2013-09-26  1:26   ` Sage Weil
2013-09-27  1:31 Stephen Rothwell
2013-09-27  2:36 ` Dave Kleikamp
2020-12-14 23:46 Stephen Rothwell

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=Pine.LNX.4.64.1009191952540.7498@cobra.newdream.net \
    --to=sage@newdream.net \
    --cc=gregf@hq.newdream.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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).