public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@infradead.org>,
	axboe@kernel.dk, matthew@wil.cx, linux-scsi@vger.kernel.org
Subject: Re: Thin provisioning update
Date: Tue, 10 Nov 2009 18:06:46 -0500	[thread overview]
Message-ID: <yq1fx8mm12x.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1257880209.4184.438.camel@mulgrave.site> (James Bottomley's message of "Tue, 10 Nov 2009 14:10:09 -0500")

>>>>> "James" == James Bottomley <James.Bottomley@HansenPartnership.com> writes:

James> SCSI pretty much pioneered the use of postmerge trees, which is
James> how I do this ... if everyone's happy, that's what I'll do this
James> time.

In the meantime I'll try to keep my TP branch up to date for people who
want to tinker with this.

  http://www.kernel.org/pub/scm/linux/kernel/git/mkp/linux-2.6-mkp.git

-- 
Martin K. Petersen	Oracle Linux Engineering

      reply	other threads:[~2009-11-10 23:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04  4:25 Thin provisioning update Martin K. Petersen
2009-11-04  4:25 ` [PATCH 1/2] block: Expose discard granularity Martin K. Petersen
2009-11-04  4:25 ` [PATCH 2/2] sd: WRITE SAME(16) / UNMAP support Martin K. Petersen
2009-11-09 14:20 ` Thin provisioning update Christoph Hellwig
2009-11-09 19:34   ` Christoph Hellwig
2009-11-10  5:37     ` Martin K. Petersen
2009-11-10 10:51       ` Jens Axboe
2009-11-10 13:16       ` Christoph Hellwig
2009-11-10 18:58         ` Martin K. Petersen
2009-11-10 19:10           ` James Bottomley
2009-11-10 23:06             ` Martin K. Petersen [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=yq1fx8mm12x.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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