From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: fs: move bdev code out of buffer.c
Date: Thu, 2 Apr 2009 22:21:07 +1100 [thread overview]
Message-ID: <200904022221.07857.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <20090401111003.GZ28946@ZenIV.linux.org.uk>
On Wednesday 01 April 2009 22:10:03 Al Viro wrote:
> On Mon, Mar 30, 2009 at 11:55:24AM -0700, Andrew Morton wrote:
> > This patch moved the CONFIG_BLOCK=y declaration of freeze_bdev() out of
> > buffer_head.h and into fs.h. But it left the CONFIG_BLOCK=n definition
> > of freeze_bdev() in buffer_head.h.
>
> Actually, there's more.
> a) fsync_bdev() export is left behind in buffer.c
> b) sync_blockdev/invalidate_bdev are like freeze_bdev/thaw_bdev -
> non-block stubs need to be moved.
>
> Fixed and pushed into for-next
Sorry about that, thanks. I always forget to test CONFIG_BLOCK=n :(
prev parent reply other threads:[~2009-04-02 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200903280059.n2S0xvhK006987@hera.kernel.org>
2009-03-30 18:55 ` Andrew Morton
2009-04-01 11:10 ` Al Viro
2009-04-02 11:21 ` Nick Piggin [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=200904022221.07857.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®