From: Jens Axboe <axboe@kernel.dk>
To: Daniel Ehrenberg <dehrenberg@google.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>,
Gwendal Grignou <gwendal@chromium.org>
Subject: Re: [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes
Date: Wed, 15 Apr 2015 13:30:24 -0600 [thread overview]
Message-ID: <552EBC50.6060901@kernel.dk> (raw)
In-Reply-To: <CAAK6Zt27UwQrKiqLf_DEAsUsMKrUYPSdSASBoE0q-yQ8wizwMg@mail.gmail.com>
On 04/15/2015 11:49 AM, Daniel Ehrenberg wrote:
> Thanks for the quick feedback. This should be fixed in v2. What do you think?
I didn't find any other issues in the previous posting, so I added the
doc bits and changed the writetrim to trimwrite. Any other differences
between master and your v2 posting? If so, separate them out and send it
in and I'll get it applied.
--
Jens Axboe
next prev parent reply other threads:[~2015-04-15 19:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 22:58 [PATCH 0/7] Framework for NAND lifetime testing Dan Ehrenberg
2015-04-14 22:58 ` [PATCH 1/7] Allow trim on any file type Dan Ehrenberg
2015-04-14 22:58 ` [PATCH 2/7] Add new writetrim rw= mode for trims preceding writes Dan Ehrenberg
2015-04-15 0:43 ` Jens Axboe
2015-04-15 17:49 ` Daniel Ehrenberg
2015-04-15 19:30 ` Jens Axboe [this message]
2015-04-15 20:28 ` Daniel Ehrenberg
2015-04-15 21:02 ` Jens Axboe
2015-04-14 22:58 ` [PATCH 3/7] Collect a block-wise histogram of trim and write errors Dan Ehrenberg
2015-04-14 22:58 ` [PATCH 4/7] mtd: Add CONFIG_MTD to ./configure script Dan Ehrenberg
2015-04-14 22:58 ` [PATCH 5/7] mtd: Import libmtd with modifications to make it compile Dan Ehrenberg
2015-04-14 22:58 ` [PATCH 6/7] mtd: ioengine Dan Ehrenberg
2015-04-14 22:58 ` [PATCH 7/7] mtd: example job file Dan Ehrenberg
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=552EBC50.6060901@kernel.dk \
--to=axboe@kernel.dk \
--cc=dehrenberg@google.com \
--cc=fio@vger.kernel.org \
--cc=gwendal@chromium.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