From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: 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 14:10:09 -0500 [thread overview]
Message-ID: <1257880209.4184.438.camel@mulgrave.site> (raw)
In-Reply-To: <yq18weenr4y.fsf@sermon.lab.mkp.net>
On Tue, 2009-11-10 at 13:58 -0500, Martin K. Petersen wrote:
> >>>>> "Christoph" == Christoph Hellwig <hch@infradead.org> writes:
>
> >> Ok. Jens, please queue the patch below. And then we'll have to see
> >> about getting James to rebase and/or postpone the SCSI portion to
> >> round #2.
>
> Christoph> Can't we please get both patches in through one tree?
> Christoph> Everything else is a bit of a pain to manage.
>
> I'm intimately familiar with said pain. Pretty much everything I do
> touches both block and scsi :/
>
> But James has been pretty good about rebasing scsi-misc on top of Jens'
> tree. That's how we've done all the other tricky merges.
>
> James, what do you think?
SCSI pretty much pioneered the use of postmerge trees, which is how I do
this ... if everyone's happy, that's what I'll do this time.
James
next prev parent reply other threads:[~2009-11-10 19:10 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 [this message]
2009-11-10 23:06 ` Martin K. Petersen
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=1257880209.4184.438.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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