Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Abhishek Chauhan (ABC)" <quic_abchauha@quicinc.com>
To: Yanteng Si <si.yanteng@linux.dev>,
	Jitendra Vegiraju <jitendra.vegiraju@broadcom.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
	"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
	<netdev@vger.kernel.org>, <alexandre.torgue@foss.st.com>,
	<joabreu@synopsys.com>, <davem@davemloft.net>,
	<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<mcoquelin.stm32@gmail.com>,
	<bcm-kernel-feedback-list@broadcom.com>,
	<richardcochran@gmail.com>, <ast@kernel.org>,
	<daniel@iogearbox.net>, <hawk@kernel.org>,
	<john.fastabend@gmail.com>, <fancer.lancer@gmail.com>,
	<ahalaney@redhat.com>, <xiaolei.wang@windriver.com>,
	<rohan.g.thomas@intel.com>, <Jianheng.Zhang@synopsys.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>, <bpf@vger.kernel.org>,
	<linux@armlinux.org.uk>, <horms@kernel.org>,
	<florian.fainelli@broadcom.com>,
	Sagar Cheluvegowda <quic_scheluve@quicinc.com>
Subject: Re: [PATCH net-next v6 0/5] net: stmmac: Add PCI driver support for BCM8958x
Date: Wed, 28 May 2025 22:24:58 -0700	[thread overview]
Message-ID: <4a2d8151-9dfe-4876-8216-85211bc393bf@quicinc.com> (raw)
In-Reply-To: <eb591c65-0106-45f4-9e57-434dac54e923@linux.dev>



On 5/28/2025 10:14 PM, Yanteng Si wrote:
> 
> 在 5/29/25 10:56 AM, Jitendra Vegiraju 写道:
>> Hi Yanteng,
>>
>> On Wed, May 28, 2025 at 6:36 PM Yanteng Si <si.yanteng@linux.dev> wrote:
>>> 在 5/28/25 8:04 AM, Abhishek Chauhan (ABC) 写道:
>>>>
>>>> On 2/7/2025 3:18 PM, Jitendra Vegiraju wrote:
>>>>> Hi Abhishek,
>>>>>
>>>>> On Fri, Feb 7, 2025 at 10:21 AM Abhishek Chauhan (ABC) <
>>>>> quic_abchauha@quicinc.com> wrote:
>>>>>
>>>>>>
>>>>>> On 11/5/2024 8:12 AM, Jitendra Vegiraju wrote:
>>>>>>> Hi netdev team,
>>>>>>>
>>>>>>> On Fri, Oct 18, 2024 at 1:53 PM <jitendra.vegiraju@broadcom.com> wrote:
>>>>>>>> From: Jitendra Vegiraju <jitendra.vegiraju@broadcom.com>
>>>>>>>>
>>>>>>>> This patchset adds basic PCI ethernet device driver support for Broadcom
>>>>>>>> BCM8958x Automotive Ethernet switch SoC devices.
>>>>>>>>
>>>>>>> I would like to seek your guidance on how to take this patch series
>>>>>> forward.
>>>>>>> Thanks to your feedback and Serge's suggestions, we made some forward
>>>>>>> progress on this patch series.
>>>>>>> Please make any suggestions to enable us to upstream driver support
>>>>>>> for BCM8958x.
>>>>>> Jitendra,
>>>>>>            Have we resent this patch or got it approved ? I dont see any
>>>>>> updates after this patch.
>>>>>>
>>>>>>
>>>>> Thank you for inquiring about the status of this patch.
>>>>> As stmmac driver is going through a maintainer transition, we wanted to
>>>>> wait until a new maintainer is identified.
>>>>> We would like to send the updated patch as soon as possible.
>>>>> Thanks,
>>>>> Jitendra
>>>> Thanks Jitendra, I am sorry but just a follow up.
>>>>
>>>> Do we know if stmmac maintainer are identified now ?
>>> I'm curious why such a precondition is added?
>>>
>> It's not a precondition. Let me give some context.
>> This patch series adds support for a new Hyper DMA(HDMA) MAC from Synopsis.
>> Many of the netdev community members reviewed the patches at that time.
>> Being the module maintainer at that time, Serge took the initiative to
>> guide us through integrating the new MAC into the stmmac driver.
>> We addressed all the review comments and submitted the last patch series.
>> Without an official maintainer, we didn't get feedback on the last patch series.
>> Because of this, we wanted to wait until a new maintainer is assigned
>> to this module.
>> As Abhishek expressed in his email, it appears the HDMA MAC is
>> becoming more mainstream.
>> We are hoping to rebase the patch series and resubmit for review if
>> netdev team members show interest.
> 
> 
> https://lore.kernel.org/netdev/20241018205332.525595-1-jitendra.vegiraju@broadcom.com/
> 
> In my opinion, the precondition for waiting for a maintainer is that
> 
> the patch set has passed the review. I checked lore and did not find
> 
> any R&B tags in the patch set, which means your patch set has not
> 
> yet met the merging requirements.
> 
> Therefore, I think you can continue to push forward with this patch
> 
> set and not let it stagnate. I will take some time to review the previous
> 
> versions (which may take a while) and hope to be helpful.
> 
> Thanks,
> 
> Yanteng
> 
I will review the patch in the coming few days as well. As this patch also helps Qualcomm to develop the 
HDMA arch for 25XGMAC EMAC controller. 
This patch is validated/verfied/tested on Qualcomm platform devices which are not PCIE based. 
>> Thanks,
>> Jitendra
>>> Thanks,
>>> Yanteng


      reply	other threads:[~2025-05-29  5:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 20:53 [PATCH net-next v6 0/5] net: stmmac: Add PCI driver support for BCM8958x jitendra.vegiraju
2024-10-18 20:53 ` [PATCH net-next v6 1/5] net: stmmac: Add snps_id, dev_id to struct plat_stmmacenet_data jitendra.vegiraju
2024-10-18 20:53 ` [PATCH net-next v6 2/5] net: stmmac: Add basic dw25gmac support in stmmac core jitendra.vegiraju
2024-10-24  1:35   ` Abhishek Chauhan (ABC)
2024-10-24  5:21     ` Abhishek Chauhan (ABC)
2024-10-18 20:53 ` [PATCH net-next v6 3/5] net: stmmac: Integrate dw25gmac into stmmac hwif handling jitendra.vegiraju
2024-10-18 20:53 ` [PATCH net-next v6 4/5] net: stmmac: Add PCI driver support for BCM8958x jitendra.vegiraju
2024-10-18 20:53 ` [PATCH net-next v6 5/5] net: stmmac: Add BCM8958x driver to build system jitendra.vegiraju
2024-10-21 11:05 ` [PATCH net-next v6 0/5] net: stmmac: Add PCI driver support for BCM8958x Serge Semin
2024-10-21 16:01   ` Jitendra Vegiraju
2024-11-05 16:12 ` Jitendra Vegiraju
2025-02-07 18:21   ` Abhishek Chauhan (ABC)
     [not found]     ` <CAMdnO-+HwXf7c=igt2j6VHcki3cYanXpFApZDcEe7DibDz810g@mail.gmail.com>
2025-05-28  0:04       ` Abhishek Chauhan (ABC)
2025-05-28  7:58         ` Russell King (Oracle)
2025-05-29  1:35         ` Yanteng Si
2025-05-29  2:56           ` Jitendra Vegiraju
2025-05-29  5:14             ` Yanteng Si
2025-05-29  5:24               ` Abhishek Chauhan (ABC) [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=4a2d8151-9dfe-4876-8216-85211bc393bf@quicinc.com \
    --to=quic_abchauha@quicinc.com \
    --cc=Jianheng.Zhang@synopsys.com \
    --cc=ahalaney@redhat.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew@lunn.ch \
    --cc=ast@kernel.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=fancer.lancer@gmail.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=jitendra.vegiraju@broadcom.com \
    --cc=joabreu@synopsys.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=linux@armlinux.org.uk \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=quic_scheluve@quicinc.com \
    --cc=richardcochran@gmail.com \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=rohan.g.thomas@intel.com \
    --cc=si.yanteng@linux.dev \
    --cc=xiaolei.wang@windriver.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