From: Christoph Hellwig <hch@lst.de>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Christoph Hellwig <hch@lst.de>,
viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH 09/10] add RWF_DSYNC aand RWF_SYNC
Date: Wed, 30 Mar 2016 08:54:20 +0200 [thread overview]
Message-ID: <20160330065420.GA8405@lst.de> (raw)
In-Reply-To: <53D41BC3-65A3-48BB-B2CC-540EBF86A2EC@dilger.ca>
On Tue, Mar 29, 2016 at 01:34:50PM -0600, Andreas Dilger wrote:
> Is it right that both of these flags are defined as "2"? From the code
> they look like they should be different values.
Yes, they should. I did the same trick as we do for __O_SYNC earlier
but then changed it last minute. I'll fix it up for the next version.
next prev parent reply other threads:[~2016-03-30 6:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 17:37 add RWF_(D)SYNC flag to preadv2/pwritev2 Christoph Hellwig
2016-03-29 17:37 ` [PATCH 01/10] filemap: remove pos variables in generic_file_read_iter Christoph Hellwig
2016-03-29 17:37 ` [PATCH 02/10] filemap: remove the pos argument to generic_file_direct_write Christoph Hellwig
2016-03-29 17:37 ` [PATCH 03/10] xfs: eliminate the pos variable in xfs_file_dio_aio_write Christoph Hellwig
2016-03-29 17:37 ` [PATCH 04/10] direct-io: eliminate the offset argument to ->direct_IO Christoph Hellwig
2016-03-29 17:37 ` [PATCH 05/10] direct-io: remove the offset argument to dio_complete Christoph Hellwig
2016-03-29 17:37 ` [PATCH 06/10] fs: add IOCB_SYNC and IOCB_DSYNC Christoph Hellwig
2016-03-29 17:37 ` [PATCH 07/10] fs: simplify the generic_write_sync prototype Christoph Hellwig
2016-03-29 19:33 ` [PATCH 07/10] " Andreas Dilger
2016-03-29 17:37 ` [PATCH 08/10] ceph: use generic_write_sync Christoph Hellwig
2016-03-29 17:37 ` [PATCH 09/10] fs: add RWF_DSYNC aand RWF_SYNC Christoph Hellwig
2016-03-29 19:34 ` [PATCH 09/10] " Andreas Dilger
2016-03-30 6:54 ` Christoph Hellwig [this message]
2016-03-29 17:37 ` [PATCH 10/10] nfsd: use RWF_SYNC Christoph Hellwig
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=20160330065420.GA8405@lst.de \
--to=hch@lst.de \
--cc=adilger@dilger.ca \
--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).