From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
jens.axboe@oracle.com, hch@infradead.org, willy@wil.cx,
jgarzik@pobox.com, sandeen@redhat.com, rwheeler@redhat.com,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Thin provisioning fixes (take 3)
Date: Thu, 26 Nov 2009 12:27:20 -0500 [thread overview]
Message-ID: <yq14oohb3if.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1259255380.7584.64.camel@mulgrave.site> (James Bottomley's message of "Thu, 26 Nov 2009 11:09:40 -0600")
>>>>> "James" == James Bottomley <James.Bottomley@suse.de> writes:
James> So you forgot to specify ordering. I think the right ordering is
James> that actually, there isn't any. Jens can take 1, I can take 2,3
James> and Jeff can take 4,5 without running any postmerge trees ... is
James> that correct?
The only dependency is that the sd patch (#2) requires "block: Expose
discard granularity" (86b37281411cf1e9bc0a6b5406c45edb7bd9ea5d) in Jens'
for-2.6.33 tree.
So we will need either a rebase or a postmerge tree.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2009-11-26 17:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 17:00 Thin provisioning fixes (take 3) Martin K. Petersen
2009-11-26 17:00 ` [PATCH 1/5] block: Allow devices to indicate whether discarded blocks are zeroed Martin K. Petersen
2009-11-26 17:00 ` [PATCH 2/5] sd: WRITE SAME(16) / UNMAP support Martin K. Petersen
2009-11-26 17:00 ` [PATCH 3/5] scsi: Correctly handle thin provisioning write error Martin K. Petersen
2009-11-26 17:00 ` [PATCH 4/5] libata: Report zeroed read after Trim and max discard size Martin K. Petersen
2009-11-27 1:55 ` Mark Lord
2009-11-27 3:46 ` Martin K. Petersen
2009-12-03 7:57 ` Jeff Garzik
2009-12-03 23:02 ` Jeff Garzik
2009-11-26 17:00 ` [PATCH 5/5] libata: Clarify ata_set_lba_range_entries function Martin K. Petersen
2009-12-03 23:02 ` Jeff Garzik
2009-11-26 17:09 ` Thin provisioning fixes (take 3) James Bottomley
2009-11-26 17:27 ` 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=yq14oohb3if.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@suse.de \
--cc=hch@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rwheeler@redhat.com \
--cc=sandeen@redhat.com \
--cc=willy@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;
as well as URLs for NNTP newsgroup(s).