From: Christian Stroetmann <stroetmann@ontolinux.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 2/4] fs: fold invalidate_list into invalidate_inodes
Date: Sun, 24 Oct 2010 23:45:52 +0200 [thread overview]
Message-ID: <4CC4A910.1010507@ontolinux.com> (raw)
In-Reply-To: <20101024174033.GB2718@lst.de>
Aloha;
Just only a typo, maybe
On the 24.10.2010 19:40, Christoph Hellwig wrote:
> Signed-off-by: Christoph Hellwig<hch@lst.de>
>
> Index: linux-2.6/fs/inode.c
> ===================================================================
> --- linux-2.6.orig/fs/inode.c 2010-10-24 16:31:49.000000000 +0200
> +++ linux-2.6/fs/inode.c 2010-10-24 16:32:20.609254420 +0200
> @@ -477,15 +477,24 @@ static void dispose_list(struct list_hea
> }
> }
>
> -/*
> - * Invalidate all inodes for a device.
> +/**
> + * invalidate_inodes - attempt to free all inodes on a superblock
> + * @sb: superblock to operate on
> + *
> + * Attempts to free all inodes for a given superblock. If there were any
> + * busy inodes return a non-zero value, else zero.
maybe:
, then return a
[...]
Have fun
Christian Stroetmann
next prev parent reply other threads:[~2010-10-24 21:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 17:40 [PATCH 1/4] fs: do not drop inode_lock in dispose_list Christoph Hellwig
2010-10-24 17:40 ` [PATCH 2/4] fs: fold invalidate_list into invalidate_inodes Christoph Hellwig
2010-10-24 21:45 ` Christian Stroetmann [this message]
2010-10-24 17:40 ` [PATCH 3/4] fs: skip I_FREEING inodes in writeback_sb_inodes Christoph Hellwig
2010-10-24 21:46 ` Christian Stroetmann
2010-10-24 17:40 ` [PATCH 4/4] fs: kill I_WILL_FREE Christoph Hellwig
2010-10-24 21:46 ` Christian Stroetmann
2010-10-24 21:50 ` Christian Stroetmann
2010-10-26 1:28 ` Al Viro
2010-10-26 19:18 ` Al Viro
2010-10-25 5:33 ` [PATCH 1/4] fs: do not drop inode_lock in dispose_list Dave Chinner
2010-10-25 5:46 ` Dave Chinner
2010-10-25 9:20 ` Dave Chinner
2010-10-25 10:07 ` Christoph Hellwig
2010-10-25 23:07 ` Dave Chinner
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=4CC4A910.1010507@ontolinux.com \
--to=stroetmann@ontolinux.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@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 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.