From: Christoph Hellwig <hch@lst.de>
To: viro@ZenIV.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org
Subject: Re: add RWF_(D)SYNC flag to preadv2/pwritev2 V2
Date: Mon, 25 Apr 2016 13:48:44 +0200 [thread overview]
Message-ID: <20160425114844.GA15496@lst.de> (raw)
In-Reply-To: <1460044324-5298-1-git-send-email-hch@lst.de>
All, can you pick this up for for-next so that it gets some time
in linux-next? Thanks!
prev parent reply other threads:[~2016-04-25 11:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 15:51 add RWF_(D)SYNC flag to preadv2/pwritev2 V2 Christoph Hellwig
2016-04-07 15:51 ` [PATCH 01/10] filemap: remove pos variables in generic_file_read_iter Christoph Hellwig
2016-04-07 15:51 ` [PATCH 02/10] filemap: remove the pos argument to generic_file_direct_write Christoph Hellwig
2016-04-07 15:51 ` [PATCH 03/10] xfs: eliminate the pos variable in xfs_file_dio_aio_write Christoph Hellwig
2016-04-07 22:31 ` Dave Chinner
2016-04-07 22:43 ` Christoph Hellwig
2016-04-07 22:50 ` Dave Chinner
2016-04-07 15:51 ` [PATCH 04/10] direct-io: eliminate the offset argument to ->direct_IO Christoph Hellwig
2016-04-07 15:51 ` [PATCH 05/10] direct-io: remove the offset argument to dio_complete Christoph Hellwig
2016-04-07 15:52 ` [PATCH 06/10] fs: add IOCB_SYNC and IOCB_DSYNC Christoph Hellwig
2016-04-07 15:52 ` [PATCH 07/10] fs: simplify the generic_write_sync prototype Christoph Hellwig
2016-04-07 15:52 ` [PATCH 08/10] ceph: use generic_write_sync Christoph Hellwig
2016-04-07 15:52 ` [PATCH 09/10] fs: add RWF_DSYNC aand RWF_SYNC Christoph Hellwig
2016-08-06 21:45 ` Michael Kerrisk (man-pages)
2016-08-09 8:15 ` Christoph Hellwig
2016-09-04 4:56 ` Michael Kerrisk (man-pages)
2016-04-07 15:52 ` [PATCH 10/10] nfsd: use RWF_SYNC Christoph Hellwig
2016-04-25 11:48 ` Christoph Hellwig [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=20160425114844.GA15496@lst.de \
--to=hch@lst.de \
--cc=linux-api@vger.kernel.org \
--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 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).