qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Laurent Vivier <lvivier@redhat.com>
Cc: qemu-devel@nongnu.org, Thomas Huth <thuth@redhat.com>,
	Marcel Apfelbaum <marcel@redhat.com>,
	qemu-ppc@nongnu.org, "Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 0/2] spapr: generate DT node names
Date: Fri, 24 Feb 2017 15:46:30 +1100	[thread overview]
Message-ID: <20170224044630.GU17615@umbus.fritz.box> (raw)
In-Reply-To: <20170217133134.10735-1-lvivier@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1788 bytes --]

On Fri, Feb 17, 2017 at 02:31:32PM +0100, Laurent Vivier wrote:
1;4601;0c> This series is a rebased series from September 2015, it has been
> reviewed but has never reached the master branch.
> 
> When DT node names for PCI devices are generated by SLOF,
> they are generated according to the type of the device
> (for instance, ethernet for virtio-net-pci device).
> 
> Node name for hotplugged devices is generated by QEMU.
> This series adds the mechanic to QEMU to create the node
> name according to the device type too.

Applied to ppc-for-2.9, thanks.

> 
> v6: rebase on master
> 
> [Wed, 30 Sep 2015]
> v5: store subclass and iface ids as-is (int) and mask them when
>     we compare them.
> 
> v4: move pci_ids.h to a separate patch, fix PCI_CLASS_NETWORK_WORDFIP
>     remove  duplicate NL, remove 386, 486 and alpha subclasses
>     rename "unknown-legacy-device", correctly check array size
>     add Thomas and Michael "Reviewed-by".
> 
> v3: use values from pci_ids.h, update pci_ids.h values
>     keep only details for USB (xhci, ohci, ...) and PIC (IO-APIC, IO-XAPIC)
> 
> v2: Use CamelCase name, remove misc-* name,
>     remove _OTHER entries to fallback to class name (as SLOF does).
>     Fix typo (IPMI-bltr).
> 
> Laurent Vivier (2):
>   PCI: add missing classes in pci_ids.h to build device tree
>   spapr: generate DT node names
> 
>  hw/ppc/spapr_pci.c       | 290 ++++++++++++++++++++++++++++++++++++++++++++---
>  include/hw/pci/pci_ids.h | 112 ++++++++++++++++--
>  2 files changed, 379 insertions(+), 23 deletions(-)
> 

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2017-02-24  5:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17 13:31 [Qemu-devel] [PATCH v6 0/2] spapr: generate DT node names Laurent Vivier
2017-02-17 13:31 ` [Qemu-devel] [PATCH v6 1/2] PCI: add missing classes in pci_ids.h to build device tree Laurent Vivier
2017-02-17 13:31 ` [Qemu-devel] [PATCH v6 2/2] spapr: generate DT node names Laurent Vivier
2017-02-24  4:46 ` David Gibson [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=20170224044630.GU17615@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=thuth@redhat.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).