qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: Cao jin <caoj.fnst@cn.fujitsu.com>, qemu-devel@nongnu.org
Cc: jiri@resnulli.us, mst@redhat.com, jasowang@redhat.com,
	alex.williamson@redhat.com, sfeldma@gmail.com, hare@suse.de,
	dmitry@daynix.com, pbonzini@redhat.com, jsnow@redhat.com,
	emu-block@nongnu.org, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH 0/2] Preparation for PCI devices convert to realize()
Date: Mon, 7 Dec 2015 15:42:19 +0200	[thread overview]
Message-ID: <56658CBB.10009@gmail.com> (raw)
In-Reply-To: <1449475725-16453-1-git-send-email-caoj.fnst@cn.fujitsu.com>

On 12/07/2015 10:08 AM, Cao jin wrote:
> There are many PCI devices still using .init() as its initialization function,
> I am planning to do the "convert to realize()" work, and PCI bridge devices are
> chosen first. The supporting functions should be modified first.msi_init() &
> msix_init() are supporting functions for PCI devices.
>
> Because this patchset is much different from the previous one, so, didn`t
> add "V2" in the subject

Hi,

Even if the patches are different is worth mentioning V2, otherwise
the maintainer would not know which to take.

Thanks,
Marcel

>
> Cao jin (2):
>    Add param Error** to msi_init() & modify the callers
>    Add param Error** to msix_init() & modify the callers
>
>   hw/audio/intel-hda.c               |  7 ++++++-
>   hw/ide/ich.c                       |  2 +-
>   hw/net/rocker/rocker.c             |  3 ++-
>   hw/net/vmxnet3.c                   |  7 +++++--
>   hw/pci-bridge/ioh3420.c            |  6 +++++-
>   hw/pci-bridge/pci_bridge_dev.c     |  6 +++++-
>   hw/pci-bridge/xio3130_downstream.c |  7 ++++++-
>   hw/pci-bridge/xio3130_upstream.c   |  7 ++++++-
>   hw/pci/msi.c                       | 17 +++++++++++++----
>   hw/pci/msix.c                      | 13 ++++++++++---
>   hw/scsi/megasas.c                  | 28 +++++++++++++++++++++-------
>   hw/scsi/vmw_pvscsi.c               |  3 ++-
>   hw/usb/hcd-xhci.c                  |  7 +++++--
>   hw/vfio/pci.c                      |  7 +++++--
>   include/hw/pci/msi.h               |  4 ++--
>   include/hw/pci/msix.h              |  3 ++-
>   16 files changed, 96 insertions(+), 31 deletions(-)
>

  parent reply	other threads:[~2015-12-07 13:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07  8:08 [Qemu-devel] [PATCH 0/2] Preparation for PCI devices convert to realize() Cao jin
2015-12-07  8:08 ` [Qemu-devel] [PATCH 1/2] Add param Error** to msi_init() & modify the callers Cao jin
2015-12-07  9:59   ` Markus Armbruster
2015-12-08 13:23     ` Cao jin
2015-12-08 15:01       ` Markus Armbruster
2015-12-09  8:54         ` Cao jin
2015-12-07  8:08 ` [Qemu-devel] [PATCH 2/2] Add param Error** to msix_init() " Cao jin
2015-12-07 13:42 ` Marcel Apfelbaum [this message]
2015-12-08  1:27   ` [Qemu-devel] [PATCH 0/2] Preparation for PCI devices convert to realize() Cao jin

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=56658CBB.10009@gmail.com \
    --to=marcel.apfelbaum@gmail.com \
    --cc=alex.williamson@redhat.com \
    --cc=caoj.fnst@cn.fujitsu.com \
    --cc=dmitry@daynix.com \
    --cc=emu-block@nongnu.org \
    --cc=hare@suse.de \
    --cc=jasowang@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=jsnow@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sfeldma@gmail.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).