From: David Gibson <david@gibson.dropbear.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: qemu-ppc@nongnu.org, Greg Kurz <groug@kaod.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] ppc/pnv: minor XSCOM fixes
Date: Wed, 11 Dec 2019 10:46:36 +1100 [thread overview]
Message-ID: <20191210234636.GO207300@umbus.fritz.box> (raw)
In-Reply-To: <20191210135845.19773-1-clg@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
On Tue, Dec 10, 2019 at 02:58:43PM +0100, Cédric Le Goater wrote:
> Hello,
>
> Here are a couple of fixes/cleanups for the PowerNV XSCOM bus.
Applied to ppc-for-5.0, thanks.
>
> Thanks,
>
> C.
>
> Cédric Le Goater (2):
> ppc/pnv: Loop on the whole hierarchy to populate the DT with the XSCOM
> nodes
> ppc/pnv: populate the DT with realized XSCOM devices
>
> hw/ppc/pnv_xscom.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 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: 833 bytes --]
prev parent reply other threads:[~2019-12-11 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 13:58 [PATCH 0/2] ppc/pnv: minor XSCOM fixes Cédric Le Goater
2019-12-10 13:58 ` [PATCH 1/2] ppc/pnv: Loop on the whole hierarchy to populate the DT with the XSCOM nodes Cédric Le Goater
2019-12-10 16:49 ` Greg Kurz
2019-12-10 17:08 ` Cédric Le Goater
2019-12-10 18:04 ` Cédric Le Goater
2019-12-10 23:46 ` David Gibson
2019-12-10 21:24 ` Greg Kurz
2019-12-10 13:58 ` [PATCH 2/2] ppc/pnv: populate the DT with realized XSCOM devices Cédric Le Goater
2019-12-10 16:53 ` Greg Kurz
2019-12-10 17:08 ` Cédric Le Goater
2019-12-10 21:24 ` Greg Kurz
2019-12-10 23: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=20191210234636.GO207300@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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).