From: Boaz Harrosh <bharrosh@panasas.com>
To: Christoph Hellwig <hch@lst.de>
Cc: viro@zeniv.linux.org.uk, akpm@linux-foundation.org,
linux-fsdevel@vger.kernel.org, Trond.Myklebust@netapp.com
Subject: Re: [PATCH 2/2] pass writeback_control to ->write_inode
Date: Tue, 12 Jan 2010 14:54:58 +0200 [thread overview]
Message-ID: <4B4C7122.6050409@panasas.com> (raw)
In-Reply-To: <20100111173100.GB6852@lst.de>
On 01/11/2010 07:31 PM, Christoph Hellwig wrote:
<snip>
> Index: linux-2.6/fs/exofs/exofs.h
> ===================================================================
> --- linux-2.6.orig/fs/exofs/exofs.h 2010-01-11 15:53:03.000000000 +0100
> +++ linux-2.6/fs/exofs/exofs.h 2010-01-11 16:12:12.278005468 +0100
> @@ -226,7 +226,7 @@ int exofs_write_begin(struct file *file,
> struct page **pagep, void **fsdata);
> extern struct inode *exofs_iget(struct super_block *, unsigned long);
> struct inode *exofs_new_inode(struct inode *, int);
> -extern int exofs_write_inode(struct inode *, int);
> +extern int exofs_write_inode(struct inode *, struct writeback_control *wbc);
> extern void exofs_delete_inode(struct inode *);
>
> /* dir.c: */
> Index: linux-2.6/fs/exofs/inode.c
> ===================================================================
> --- linux-2.6.orig/fs/exofs/inode.c 2010-01-11 15:53:03.000000000 +0100
> +++ linux-2.6/fs/exofs/inode.c 2010-01-11 16:12:12.280004047 +0100
> @@ -1238,9 +1238,9 @@ out:
> return ret;
> }
>
> -int exofs_write_inode(struct inode *inode, int wait)
> +int exofs_write_inode(struct inode *inode, struct writeback_control *wbc)
> {
> - return exofs_update_inode(inode, wait);
> + return exofs_update_inode(inode, wbc->sync_mode == WB_SYNC_ALL);
> }
>
> /*
<snip>
ACK-by: Boaz Harrosh <bharrosh@panasas.com>
prev parent reply other threads:[~2010-01-12 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 17:31 [PATCH 2/2] pass writeback_control to ->write_inode Christoph Hellwig
2010-01-12 0:43 ` Dave Chinner
2010-01-12 12:54 ` Boaz Harrosh [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=4B4C7122.6050409@panasas.com \
--to=bharrosh@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@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 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.