From: Christoph Hellwig <hch@lst.de>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: hch@lst.de, James.Bottomley@suse.de, snitzer@redhat.com,
axboe@kernel.dk, linux-scsi@vger.kernel.org, dm-devel@redhat.com,
linux-ide@vger.kernel.org
Subject: Re: [RFC 1/2] block: implement an unprep function corresponding directly to prep
Date: Mon, 5 Jul 2010 21:24:13 +0200 [thread overview]
Message-ID: <20100705192413.GA24189@lst.de> (raw)
In-Reply-To: <20100705160023S.fujita.tomonori@lab.ntt.co.jp>
On Mon, Jul 05, 2010 at 04:00:44PM +0900, FUJITA Tomonori wrote:
> Did you tested my discard branch, right?
I tested the patch that you sent out back then.
> Wired, I've just got Intel SSD X25-M drives and mkfs.xfs worked well.
What codebase were you testing on? Sorry, but curently I'm a bit lost
in the maze of patches. I've got both and intel and an OCZ SSD (right
now I'm travelling with only access to the OCZ actually) and I'd like
to test the latest variant again.
next prev parent reply other threads:[~2010-07-05 19:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 17:01 [RFC 1/2] block: implement an unprep function corresponding directly to prep James Bottomley
2010-06-30 17:10 ` [RFC 2/2] sd: free discard page in unprep function James Bottomley
2010-06-30 17:23 ` [RFC 1/2] block: implement an unprep function corresponding directly to prep Mike Snitzer
2010-06-30 17:51 ` Jens Axboe
2010-06-30 17:54 ` Martin K. Petersen
2010-07-01 1:47 ` FUJITA Tomonori
2010-07-01 3:47 ` Mike Snitzer
2010-07-01 4:44 ` [dm-devel] " FUJITA Tomonori
2010-07-02 11:03 ` Christoph Hellwig
2010-07-05 7:00 ` FUJITA Tomonori
2010-07-05 19:24 ` Christoph Hellwig [this message]
2010-07-05 21:50 ` Mark Lord
2010-07-05 21:54 ` Mark Lord
2010-07-05 22:00 ` Jeff Garzik
2010-08-03 3:01 ` Mark Lord
2010-07-06 7:04 ` FUJITA Tomonori
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=20100705192413.GA24189@lst.de \
--to=hch@lst.de \
--cc=James.Bottomley@suse.de \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=snitzer@redhat.com \
/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