From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: Christoph Hellwig <hch@lst.de>,
axboe@fb.com, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 10/16] fs: decouple READ and WRITE from the block layer ops
Date: Tue, 1 Nov 2016 15:30:46 +0100 [thread overview]
Message-ID: <20161101143046.GA17690@lst.de> (raw)
In-Reply-To: <8da714d4-067a-6fdf-0ac2-0d89a2980071@sandisk.com>
On Tue, Nov 01, 2016 at 08:23:54AM -0600, Bart Van Assche wrote:
> On 11/01/2016 07:40 AM, Christoph Hellwig wrote:
>> +/* generic data direction defintions */
>> +#define READ 0
>> +#define WRITE 1
>
> Hello Christoph,
>
> If you have to resend this patch series, please fix the spelling of
> "definitions".
Thanks Bart, that's one of my favourite misspelling that I keep getting
wrong again and again..
next prev parent reply other threads:[~2016-11-01 14:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 13:40 untange block operations and fs READ/WRITE Christoph Hellwig
2016-11-01 13:40 ` [PATCH 01/16] cfq-iosched: use op_is_sync instead of opencoding it Christoph Hellwig
2016-11-01 13:40 ` [PATCH 02/16] blk-cgroup: use op_is_sync to check for synchronous requests Christoph Hellwig
2016-11-01 13:40 ` [PATCH 03/16] umem: " Christoph Hellwig
2016-11-01 13:40 ` [PATCH 04/16] bcache: " Christoph Hellwig
2016-11-01 13:40 ` [PATCH 05/16] btrfs: " Christoph Hellwig
2016-11-01 13:40 ` [PATCH 06/16] block: don't use REQ_SYNC in the READ_SYNC definition Christoph Hellwig
2016-11-01 13:40 ` [PATCH 07/16] block: treat REQ_FUA and REQ_PREFLUSH as synchronous Christoph Hellwig
2016-11-01 13:40 ` [PATCH 08/16] block: replace REQ_NOIDLE with REQ_IDLE Christoph Hellwig
2016-11-01 13:40 ` [PATCH 09/16] block,fs: use REQ_* flags directly Christoph Hellwig
2016-11-01 13:40 ` [PATCH 10/16] fs: decouple READ and WRITE from the block layer ops Christoph Hellwig
2016-11-01 14:23 ` Bart Van Assche
2016-11-01 14:30 ` Christoph Hellwig [this message]
2016-11-01 13:40 ` [PATCH 11/16] block, fs: move submit_bio to bio.h Christoph Hellwig
2016-11-01 13:40 ` [PATCH 12/16] block,fs: untangle fs.h and blk_types.h Christoph Hellwig
2016-11-01 13:40 ` [PATCH 13/16] arm, arm64: don't include blk_types.h in <asm/io.h> Christoph Hellwig
2016-11-01 13:40 ` [PATCH 14/16] ceph: don't include blk_types.h in messenger.h Christoph Hellwig
2016-11-01 13:40 ` [PATCH 15/16] mm: only include blk_types in swap.h if CONFIG_SWAP is enabled Christoph Hellwig
2016-11-01 13:40 ` [PATCH 16/16] block: remove the CONFIG_BLOCK ifdef in blk_types.h Christoph Hellwig
2016-11-01 20:01 ` untange block operations and fs READ/WRITE Jens Axboe
2016-11-01 20:01 ` Jens Axboe
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=20161101143046.GA17690@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=bart.vanassche@sandisk.com \
--cc=linux-block@vger.kernel.org \
--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.