qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Miles Glenn <milesg@linux.vnet.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: "Nicholas Piggin" <npiggin@gmail.com>,
	"Frédéric Barrat" <fbarrat@linux.ibm.com>
Subject: Re: [PATCH v3 1/8] ppc/pnv: Add pca9552 to powernv10 for PCIe hotplug power control
Date: Fri, 17 Nov 2023 13:08:20 -0600	[thread overview]
Message-ID: <bcafd2e50df3758f5be551b36f8dbfb6f9d3197c.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <401c3b41-8344-4043-9f7d-26844fcb03cd@kaod.org>

On Fri, 2023-11-17 at 17:04 +0100, Cédric Le Goater wrote:
> > Well, I was hoping to sweep the pca9554 model under the PowerNV
> > maintainership (like pca9552 is under the BMC aspeed
> > maintainership).
> > I did update the PowerNV list to include it, but perhaps that was
> > presumptuous of me. :-)
> 
> Well, you are the person who has the most knowledge on both and
> you have access to HW to check changes !
> 
> > I would be ok with being added as a reviewer under the PowerNV
> > list,
> > but I wonder if I shouldn't have more opensource experience before
> > becoming a maintainer? TBH, I have no idea what that would entail.
> 
> For these devices, mostly acking the changes. I don't think anyone
> will ask you to send PRs. This can be handled through some other
> tree, PPC or Aspeed.
> 
Ok, that doesn't sound too bad.  Sign me up!

>   
> > As for patches 3 and 4, it sounds like I should split those changes
> > out
> > from the current patch series so that they can make it into QEMU
> > 8.2.
> > Correct?
> 
> I don't think this is needed. They can be picked in the series and
> merged in the ppc tree independently.
> 
> Thanks,
> 
> C.
> 
Ok, sounds good.

Thanks,

Glenn



  reply	other threads:[~2023-11-17 19:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 19:56 [PATCH v3 0/8] Add powernv10 I2C devices and tests Glenn Miles
2023-11-14 19:56 ` [PATCH v3 1/8] ppc/pnv: Add pca9552 to powernv10 for PCIe hotplug power control Glenn Miles
2023-11-15  7:28   ` Cédric Le Goater
2023-11-15 16:37     ` Miles Glenn
2023-11-15 22:34       ` Cédric Le Goater
2023-11-16 22:43         ` Miles Glenn
2023-11-17 16:04           ` Cédric Le Goater
2023-11-17 19:08             ` Miles Glenn [this message]
2023-11-14 19:56 ` [PATCH v3 2/8] ppc/pnv: Wire up pca9552 GPIO pins " Glenn Miles
2023-11-14 19:56 ` [PATCH v3 3/8] ppc/pnv: PNV I2C engines assigned incorrect XSCOM addresses Glenn Miles
2023-11-15 22:19   ` Cédric Le Goater
2023-11-18  7:36   ` Cédric Le Goater
2023-11-14 19:56 ` [PATCH v3 4/8] ppc/pnv: Fix PNV I2C invalid status after reset Glenn Miles
2023-11-15 22:20   ` Cédric Le Goater
2023-11-18  7:36   ` Cédric Le Goater
2023-11-14 19:56 ` [PATCH v3 5/8] ppc/pnv: Use resettable interface to reset child I2C buses Glenn Miles
2023-11-14 19:56 ` [PATCH v3 6/8] misc: Add a pca9554 GPIO device model Glenn Miles
2023-11-14 19:56 ` [PATCH v3 7/8] ppc/pnv: Add a pca9554 I2C device to powernv10 Glenn Miles
2023-11-14 19:56 ` [PATCH v3 8/8] ppc/pnv: Test pnv i2c master and connected devices Glenn Miles
2023-11-15 10:03 ` [PATCH v3 0/8] Add powernv10 I2C devices and tests Cédric Le Goater

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=bcafd2e50df3758f5be551b36f8dbfb6f9d3197c.camel@linux.vnet.ibm.com \
    --to=milesg@linux.vnet.ibm.com \
    --cc=clg@kaod.org \
    --cc=fbarrat@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --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).