From: Artem Bityutskiy <dedekind1@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: jack@suse.cz, linux-fsdevel@vger.kernel.org, dhowells@redhat.com
Subject: Re: [PATCH 3/3] ubifs: remove manual O_SYNC handling
Date: Thu, 01 Oct 2009 10:42:46 +0300 [thread overview]
Message-ID: <1254382966.32310.17.camel@localhost> (raw)
In-Reply-To: <1254382784.32310.15.camel@localhost>
On Thu, 2009-10-01 at 10:39 +0300, Artem Bityutskiy wrote:
> On Wed, 2009-09-30 at 22:17 +0200, Christoph Hellwig wrote:
> > generic_file_aio_write already calls into ->fsync to handle O_SYNC/O_DSYNC.
> > Remove the duplicate call to ubifs_sync_wbufs_by_inode which is already
> > covered by ubifs_fsync.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> Pushed to ubifs-2.6.git tree, thanks!
Just to make sure, the patch looks independent on anything else to me,
right? So I pushed it to my 2.6.32-rc1 - based tree.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-01 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 20:16 sort out lose ends after the O_SYNC series Christoph Hellwig
2009-09-30 20:16 ` [PATCH 1/3] kill wait_on_page_writeback_range Christoph Hellwig
2009-10-01 11:20 ` Jan Kara
2009-09-30 20:16 ` [PATCH 2/3]: afs: remove manual O_SYNC handling Christoph Hellwig
2009-09-30 20:17 ` [PATCH 3/3] ubifs: " Christoph Hellwig
2009-10-01 7:39 ` Artem Bityutskiy
2009-10-01 7:42 ` Artem Bityutskiy [this message]
2009-10-01 11:14 ` Jan Kara
2009-10-01 10:42 ` [PATCH 2/3]: afs: " David Howells
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=1254382966.32310.17.camel@localhost \
--to=dedekind1@gmail.com \
--cc=dhowells@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).