From: Al Viro <viro@ZenIV.linux.org.uk>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for July 16
Date: Mon, 16 Jul 2012 09:31:46 +0100 [thread overview]
Message-ID: <20120716083146.GL31729@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+icZUV1_QUyBh-PQoFy5jL5ft=neUvVyxx77PhiVgAnOCFUYA@mail.gmail.com>
On Mon, Jul 16, 2012 at 09:56:45AM +0200, Sedat Dilek wrote:
> On Mon, Jul 16, 2012 at 9:54 AM, Sedat Dilek <sedat.dilek@gmail.com> wrote:
> > On Mon, Jul 16, 2012 at 9:48 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> >> On Mon, Jul 16, 2012 at 05:17:09PM +1000, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Changes since 20120713:
> >>>
> >>> The ext4 tree lost its build failure.
> >>>
> >>> The vfs tree gained a build failure so I used the version from
> >>> next-20120713.
> >>
> >> Details, please?
> >
> > [1] http://lkml.indiana.edu/hypermail/linux/kernel/1107.2/00046.html
> >
>
> Grr right subject - wrong email, Stephen's mail seems to be not in the
> offline mail-archives, so I am quoting:
>
> "Hi Al,
>
> After merging the vfs tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> fs/ext2/super.c: In function 'ext2_sync_fs':
> fs/ext2/super.c:1191:2: error: implicit declaration of function
> 'dquot_writeback_dquots' [-Werror=implicit-function-declaration]
> fs/ext3/super.c: In function 'ext3_sync_fs':
> fs/ext3/super.c:2534:2: error: implicit declaration of function
> 'dquot_writeback_dquots' [-Werror=implicit-function-declaration]
> fs/ext4/super.c: In function 'ext4_sync_fs':
> fs/ext4/super.c:4493:2: error: implicit declaration of function
> 'dquot_writeback_dquots' [-Werror=implicit-function-declaration]
>
> Caused by commits 05566b558a47 ("quota: Move quota syncing to ->sync_fs
> method") and ad04033e79d2 ("quota: Split dquot_quota_sync() to writeback
> and cache flushing part"). Please do build testing with and without
> CONFIG QUOTA for quota changes ...
Fixed, folded and pushed...
next prev parent reply other threads:[~2012-07-16 8:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 7:17 linux-next: Tree for July 16 Stephen Rothwell
2012-07-16 7:48 ` Al Viro
2012-07-16 7:54 ` Sedat Dilek
2012-07-16 7:56 ` Sedat Dilek
2012-07-16 8:31 ` Al Viro [this message]
2012-07-16 15:32 ` [PATCH -next] staging: fix sm7xxfb build, depends on PCI Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2011-07-16 14:08 linux-next: Tree for July 16 Stephen Rothwell
2011-07-16 14:28 ` Stephen Rothwell
2011-07-16 19:14 ` Arnd Bergmann
2009-07-16 7:20 Stephen Rothwell
2008-07-16 13:50 Stephen Rothwell
2008-07-16 18:15 ` Takashi Iwai
2008-07-17 7:17 ` Tino Keitel
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=20120716083146.GL31729@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--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 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.