From: Harsh Prateek Bora <harshpb@linux.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org, clg@redhat.com
Cc: danielhb413@gmail.com, fbarrat@linux.ibm.com,
rathc@linux.ibm.com, adityag@linux.ibm.com, gautam@linux.ibm.com,
philmd@linaro.org
Subject: Re: [PATCH v2 0/5] MAINTAINERS updates for ppc/spapr/pnv/xive
Date: Tue, 5 Aug 2025 13:23:24 +0530 [thread overview]
Message-ID: <f8412eeb-ee0b-4871-9ff0-e783d50f7de1@linux.ibm.com> (raw)
In-Reply-To: <DBTNAC0PCPJN.9XCRXCPTLSC3@gmail.com>
Hi Nick,
On 8/4/25 18:03, Nicholas Piggin wrote:
> Hey Harsh,
>
> Sorry I dropped the ball on the merge window. Thanks to you and Cedric
> and others for picking it up and apologies to those I kept waiting. I
> let things overwhelm me a bit and got stressed about getting back to it
> :(
Some situations are inevitable and hope it happened earlier for good.
Thanks to you and Cedric for enabling us get on board to contribute better.
>
> I would like to keep helping out with qemu/ppc as time permits, I'll
> try not to over promise though. Apologies again.
Your guidance on PPC and in general will certainly help us to make
better decisions. Thanks very much for all your support!
regards,
Harsh
>
> Thanks,
> Nick
> `
> On Thu Jul 24, 2025 at 8:06 PM AEST, Harsh Prateek Bora wrote:
>> Some of us at IBM have been actively working/contributing in
>> ppc/spapr/pnv/xive and would like to step up to help with
>> reviews and co-maintainer activities. I have also included proposal
>> patches from Chinmay and Aditya in this patchset which had already
>> been posted to list earlier to request for merge.
>>
>> Thanks
>> Harsh
>>
>> Changelog:
>> v2: Added my S-o-b as suggested by Philippe, Cedric
>> v1: Initial patchset
>>
>> Aditya Gupta (1):
>> MAINTAINERS: Add myself as a reviewer of PowerNV emulation
>>
>> Chinmay Rath (1):
>> MAINTAINERS: Add myself as reviewer for PowerPC TCG CPUs
>>
>> Gautam Menghani (1):
>> MAINTAINERS: Add myself as a reviewer for XIVE
>>
>> Harsh Prateek Bora (2):
>> MAINTAINERS: Adding myself as a co-maintainer for ppc/spapr
>> MAINTAINERS: Adding myself as reviewer for PPC KVM cpus.
>>
>> MAINTAINERS | 5 +++++
>> 1 file changed, 5 insertions(+)
>
prev parent reply other threads:[~2025-08-05 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 10:06 [PATCH v2 0/5] MAINTAINERS updates for ppc/spapr/pnv/xive Harsh Prateek Bora
2025-07-24 10:06 ` [PATCH v2 1/5] MAINTAINERS: Adding myself as a co-maintainer for ppc/spapr Harsh Prateek Bora
2025-07-24 10:06 ` [PATCH v2 2/5] MAINTAINERS: Adding myself as reviewer for PPC KVM cpus Harsh Prateek Bora
2025-07-24 10:06 ` [PATCH v2 3/5] MAINTAINERS: Add myself as reviewer for PowerPC TCG CPUs Harsh Prateek Bora
2025-07-24 10:06 ` [PATCH v2 4/5] MAINTAINERS: Add myself as a reviewer of PowerNV emulation Harsh Prateek Bora
2025-07-24 10:06 ` [PATCH v2 5/5] MAINTAINERS: Add myself as a reviewer for XIVE Harsh Prateek Bora
2025-07-24 12:35 ` [PATCH v2 0/5] MAINTAINERS updates for ppc/spapr/pnv/xive Cédric Le Goater
2025-08-04 12:33 ` Nicholas Piggin
2025-08-04 12:42 ` Cédric Le Goater
2025-08-05 7:53 ` Harsh Prateek Bora [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=f8412eeb-ee0b-4871-9ff0-e783d50f7de1@linux.ibm.com \
--to=harshpb@linux.ibm.com \
--cc=adityag@linux.ibm.com \
--cc=clg@redhat.com \
--cc=danielhb413@gmail.com \
--cc=fbarrat@linux.ibm.com \
--cc=gautam@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rathc@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.