Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Hans Zhang <18255117159@163.com>
To: Aksh Garg <a-garg7@ti.com>,
	linux-pci@vger.kernel.org, helgaas@kernel.org,
	Manivannan Sadhasivam <mani@kernel.org>
Cc: linux-kernel@vger.kernel.org, s-vadapalli@ti.com,
	hans.zhang@cixtech.com, vigneshr@ti.com, danishanwar@ti.com
Subject: Re: [PATCH] MAINTAINERS: Add Aksh Garg as PCI CADENCE reviewer
Date: Fri, 8 May 2026 19:34:01 +0800	[thread overview]
Message-ID: <d0fb1c9b-4331-4f28-a95e-0962a2c9dd77@163.com> (raw)
In-Reply-To: <12c2c868-a734-49f9-9938-77319b35da3d@163.com>



On 5/8/26 15:08, Hans Zhang wrote:
> Hi Aksh,
> 
> Let's wait for one day, or two days, to see if Vignesh is willing to do it.
> 
> For drivers/pci/controller/cadence, currently Aksh and Siddharth hope to 
> become Reviewers. Manikandan believes that he can become a Maintainer. I 
> myself also hope to apply for the role of maintainer. Then let's review 
> the common driver related to Cadence PCIe IP, as well as the driver of 
> the product.
> 
> Siddharth:
> Depending on the frequency with which we are able to Review patches 
> consistently, we could eventually take up the role of being a Maintainer 
> as well.
> 


Hi Aksh,

Privately, Vignesh has replied as follows:

Vignesh:
Agreed, I would prefer if Manikandan can own the driver as he would have
better visibility wrt IP documentations as part of Cadence.

Sorry, I don't have the bandwidth to own the driver. Siddharth and Aksh
can help review and test on all TI platforms with Cadence PCIe IP.




Could you please add Siddharth as a Reviewer? I and Manikandan are the 
maintainers. Of course, we need to see if Bjorn and Mani agree. Then, 
send this patch in the next version.


Best regards,
Hans


> Best regards,
> Hans
> 
> On 5/8/26 14:09, Aksh Garg wrote:
>> I wish to contribute to the review process for Cadence PCIe IP drivers,
>> hence add myself as a reviewer.
>>
>> Signed-off-by: Aksh Garg <a-garg7@ti.com>
>> ---
>>   MAINTAINERS | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 2fb1c75afd16..e2c188a358ed 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -20315,10 +20315,11 @@ F:    Documentation/devicetree/bindings/pci/ 
>> marvell,armada8k-pcie.yaml
>>   F:    drivers/pci/controller/dwc/pcie-armada8k.c
>>   PCI DRIVER FOR CADENCE PCIE IP
>> +R:    Aksh Garg <a-garg7@ti.com>
>>   L:    linux-pci@vger.kernel.org
>>   S:    Orphan
>>   F:    Documentation/devicetree/bindings/pci/cdns,*
>> -F:    drivers/pci/controller/cadence/*cadence*
>> +F:    drivers/pci/controller/cadence/
>>   PCI DRIVER FOR CIX Sky1
>>   M:    Hans Zhang <hans.zhang@cixtech.com>
> 


  reply	other threads:[~2026-05-08 11:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08  6:09 [PATCH] MAINTAINERS: Add Aksh Garg as PCI CADENCE reviewer Aksh Garg
2026-05-08  7:08 ` Hans Zhang
2026-05-08 11:34   ` Hans Zhang [this message]
2026-05-11  4:25     ` Manivannan Sadhasivam
2026-05-11  7:08   ` Krzysztof Wilczyński
2026-05-08 14:15 ` Bjorn Helgaas

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=d0fb1c9b-4331-4f28-a95e-0962a2c9dd77@163.com \
    --to=18255117159@163.com \
    --cc=a-garg7@ti.com \
    --cc=danishanwar@ti.com \
    --cc=hans.zhang@cixtech.com \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=vigneshr@ti.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