public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse•cz>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org
Subject: Re: linux-next: quota tree build failure
Date: Wed, 14 Jan 2009 15:18:51 +0100	[thread overview]
Message-ID: <20090114141851.GD19950@duck.suse.cz> (raw)
In-Reply-To: <20090114121551.2dc725f9.sfr@canb.auug.org.au>

On Wed 14-01-09 12:15:51, Stephen Rothwell wrote:
> Hi Jan,
> 
> Today's linux-next build (x86_64 allmodconfig) failed like this:
> 
> fs/ocfs2/quota_global.c: In function 'ocfs2_dquot_initialize':
> fs/ocfs2/quota_global.c:858: error: implicit declaration of function 'dquot_is_cached'
> fs/ocfs2/quota_global.c: In function 'ocfs2_dquot_drop':
> fs/ocfs2/quota_global.c:962: error: implicit declaration of function 'dquot_drop_locked'
> 
> Caused by commit 39a225f20e9b881f1c9431d073a62fbf38219614 ("quota:
> Improve locking") which removes these functions.
  OK, thanks for letting me know. OCFS2 hasn't yet merged the corresponding patch. I've
removed the patch from my for_next branch for now.

										Honza
-- 
Jan Kara <jack@suse•cz>
SUSE Labs, CR

  reply	other threads:[~2009-01-14 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14  1:15 linux-next: quota tree build failure Stephen Rothwell
2009-01-14 14:18 ` Jan Kara [this message]
2009-01-14 22:23   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-01-19  2:01 Stephen Rothwell
2009-01-22  4:58 ` Stephen Rothwell
2009-02-06  3:18 Stephen Rothwell
2009-02-09 21:36 ` Jan Kara

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=20090114141851.GD19950@duck.suse.cz \
    --to=jack@suse$(echo .)cz \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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