qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Hannes Reinecke <hare@suse.de>,
	qemu-devel@nongnu.org,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 0/3][v17] megasas: LSI Megaraid SAS HBA emulation
Date: Fri, 08 Jun 2012 12:21:48 +0200	[thread overview]
Message-ID: <4FD1D23C.6040704@suse.de> (raw)
In-Reply-To: <4FD13842.8000102@redhat.com>

Am 08.06.2012 01:24, schrieb Paolo Bonzini:
> Il 29/05/2012 14:22, Paolo Bonzini ha scritto:
>> Il 29/05/2012 13:51, Hannes Reinecke ha scritto:
>>> This is an updated patchset for megasas. Upon popular demand
>>> I've split it into three parts, the header file, the emulation
>>> itself, and a patch adding trace events to the emulation.
>>>
>>> Paolo, can you merge it via your tree? Or should I ask
>>> someone else?
>>
>> Yes, of course.  I'll wait for an Acked-by or a couple of weeks,
>> whatever comes first.
> 
>> Acked-by: Alexander Graf <agraf@suse.de>
>> Tested-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
> 
> Ok, pull request coming. :)

Paolo, could you please squash the following fixups? Namely:
* Drop semicolon after type_init() - unresolved comment from v14
* Make TypeInfo const
* Revert unrelated whitespace change in pci_ids.h

I told Hannes I'd send this to spare him another resend.

It would also be good if someone could review my dependency patch,
prompted by an earlier megasas submission:
http://patchwork.ozlabs.org/patch/163647/
Maybe prepend it to this series' pci.mak change on scsi-next?

diff --git a/hw/megasas.c b/hw/megasas.c
index bf5f8cd..25e5c71 100644
--- a/hw/megasas.c
+++ b/hw/megasas.c
@@ -1935,7 +1935,7 @@ static void megasas_class_init(ObjectClass *oc,
void *data)
     dc->desc = "LSI MegaRAID SAS 1078";
 }

-static TypeInfo megasas_info = {
+static const TypeInfo megasas_info = {
     .name  = "megasas",
     .parent = TYPE_PCI_DEVICE,
     .instance_size = sizeof(MegasasState),
@@ -1947,4 +1947,4 @@ static void megasas_register_types(void)
     type_register_static(&megasas_info);
 }

-type_init(megasas_register_types);
+type_init(megasas_register_types)
diff --git a/hw/pci_ids.h b/hw/pci_ids.h
index 0306255..c2986aa 100644
--- a/hw/pci_ids.h
+++ b/hw/pci_ids.h
@@ -12,6 +12,7 @@

 #define PCI_BASE_CLASS_STORAGE           0x01
 #define PCI_BASE_CLASS_NETWORK           0x02
+
 #define PCI_CLASS_STORAGE_SCSI           0x0100
 #define PCI_CLASS_STORAGE_IDE            0x0101
 #define PCI_CLASS_STORAGE_RAID           0x0104

Thanks,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      reply	other threads:[~2012-06-08 10:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1338292278-14141-1-git-send-email-hare@suse.de>
2012-06-07 16:01 ` [Qemu-devel] [PATCH 0/3][v17] megasas: LSI Megaraid SAS HBA emulation Stefan Hajnoczi
     [not found] ` <4FC4BF7F.2010004@redhat.com>
2012-06-07 23:24   ` Paolo Bonzini
2012-06-08 10:21     ` Andreas Färber [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=4FD1D23C.6040704@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=hare@suse.de \
    --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).