qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Stefan Haynoczi <stefanha@linux.vnet.ibm.com>,
	Alexander Graf <agraf@suse.de>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] scsi fixes
Date: Tue, 19 Jul 2011 10:10:47 +0200	[thread overview]
Message-ID: <4E253C07.90008@suse.de> (raw)
In-Reply-To: <4E2534A1.4000701@redhat.com>

On 07/19/2011 09:39 AM, Kevin Wolf wrote:
> Am 19.07.2011 08:31, schrieb Hannes Reinecke:
>> On 07/12/2011 03:37 PM, Kevin Wolf wrote:
>>> Am 11.07.2011 15:02, schrieb Hannes Reinecke:
>>>> Hi all,
>>>>
>>>> these are some fixes I found during debugging my megasas HBA emulation.
>>>> This time I've sent them as a separate patchset for inclusion.
>>>> All of them have been acked, so please apply.
>>>>
>>>> Hannes Reinecke (4):
>>>>     iov: Update parameter usage in iov_(to|from)_buf()
>>>>     scsi: Add 'hba_private' to SCSIRequest
>>>>     scsi-disk: Fixup debugging statement
>>>>     scsi-disk: Mask out serial number EVPD
>>>
>>> Thanks, applied all to the block branch.
>>>
>> Any chance to have them pulled into the main tree?
>> My megasas emulation relies on them, and it feels a bit
>> stupid to send a patch relying on some fixes not in mainline.
>> At the same time it's really stupid to resend the entire
>> patchset again ...
>
> I'm hoping to send a pull request today, now that the VMDK patches look
> good finally.
>
> Anyway, I don't think that not having the patches in master yet should
> stop you from going forward with the next patches. They will go through
> the block tree anyway, so basing them on that tree is fine (and you
> wouldn't be the first one to do that). Just state in PATCH 0/n for the
> reviewers that it depends on the other patches.
>
Well, the remaining patch is 'just' the megasas emulation itself.
And I want to make reviewing that as easy as possible, so that it's 
not again being held off by complains about missing patches.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2011-07-19  8:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 13:02 [Qemu-devel] [PATCH 0/4] scsi fixes Hannes Reinecke
2011-07-11 13:02 ` [Qemu-devel] [PATCH 1/4] iov: Update parameter usage in iov_(to|from)_buf() Hannes Reinecke
2011-07-11 13:02   ` [Qemu-devel] [PATCH 2/4] scsi: Add 'hba_private' to SCSIRequest Hannes Reinecke
2011-07-11 13:02     ` [Qemu-devel] [PATCH 3/4] scsi-disk: Fixup debugging statement Hannes Reinecke
2011-07-11 13:02       ` [Qemu-devel] [PATCH 4/4] scsi-disk: Mask out serial number EVPD Hannes Reinecke
2011-07-11 13:34 ` [Qemu-devel] [PATCH 0/4] scsi fixes Stefan Hajnoczi
2011-07-11 13:42   ` Kevin Wolf
2011-07-11 13:45     ` Hannes Reinecke
2011-07-12 13:37 ` Kevin Wolf
2011-07-19  6:31   ` Hannes Reinecke
2011-07-19  7:39     ` Kevin Wolf
2011-07-19  8:10       ` Hannes Reinecke [this message]
2011-07-19  8:50         ` Alexander Graf

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=4E253C07.90008@suse.de \
    --to=hare@suse.de \
    --cc=agraf@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).