From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jan Kara <jack@suse.cz>
Cc: linux-next@vger.kernel.org
Subject: linux-next: quota tree build failure
Date: Fri, 6 Feb 2009 14:18:06 +1100 [thread overview]
Message-ID: <20090206141806.fdbd5cc3.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
Hi Jan,
Today's linux-next build (powerpc ppc64_defconfig) failed like this:
fs/nfsd/vfs.c: In function 'nfsd_setattr':
fs/nfsd/vfs.c:359: error: implicit declaration of function 'DQUOT_INIT'
Caused by commit 74d9386bc58d5f8b5bcee051e04e7123cd9cac88 ("quota: Remove
uppercase aliases for quota functions"). Seems you missed at least one
of the users.
I have dropped the quota tree for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-02-06 3:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 3:18 Stephen Rothwell [this message]
2009-02-09 21:36 ` linux-next: quota tree build failure Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2009-01-19 2:01 Stephen Rothwell
2009-01-22 4:58 ` Stephen Rothwell
2009-01-14 1:15 Stephen Rothwell
2009-01-14 14:18 ` Jan Kara
2009-01-14 22:23 ` 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=20090206141806.fdbd5cc3.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jack@suse.cz \
--cc=linux-next@vger.kernel.org \
/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