[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1432177615.717619.1740740137819.JavaMail.zimbra@couthit.local>
Date: Fri, 28 Feb 2025 16:25:37 +0530 (IST)
From: Parvathi Pudi <parvathi@...thit.com>
To: danishanwar <danishanwar@...com>
Cc: parvathi <parvathi@...thit.com>, kuba <kuba@...nel.org>,
rogerq <rogerq@...nel.org>, andrew+netdev <andrew+netdev@...n.ch>,
davem <davem@...emloft.net>, edumazet <edumazet@...gle.com>,
pabeni <pabeni@...hat.com>, robh <robh@...nel.org>,
krzk+dt <krzk+dt@...nel.org>, conor+dt <conor+dt@...nel.org>,
nm <nm@...com>, ssantosh <ssantosh@...nel.org>,
richardcochran <richardcochran@...il.com>,
basharath <basharath@...thit.com>, schnelle <schnelle@...ux.ibm.com>,
diogo ivo <diogo.ivo@...mens.com>,
m-karicheri2 <m-karicheri2@...com>, horms <horms@...nel.org>,
jacob e keller <jacob.e.keller@...el.com>,
m-malladi <m-malladi@...com>,
javier carrasco cruz <javier.carrasco.cruz@...il.com>,
afd <afd@...com>, s-anna <s-anna@...com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
netdev <netdev@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
pratheesh <pratheesh@...com>, Prajith Jayarajan <prajith@...com>,
Vignesh Raghavendra <vigneshr@...com>, praneeth <praneeth@...com>,
srk <srk@...com>, rogerq <rogerq@...com>,
krishna <krishna@...thit.com>, pmohan <pmohan@...thit.com>,
mohan <mohan@...thit.com>
Subject: Re: [PATCH net-next v3 00/10] PRU-ICSSM Ethernet Driver
Hi,
> On 18/02/25 3:36 pm, Parvathi Pudi wrote:
>>
>> Hi,
>>
>>> On Fri, 14 Feb 2025 11:16:52 +0530 parvathi wrote:
>>>> The Programmable Real-Time Unit Industrial Communication Sub-system (PRU-ICSS)
>>>> is available on the TI SOCs in two flavors: Gigabit ICSS (ICSSG) and the older
>>>> Megabit ICSS (ICSSM).
>>>
>>> Every individual patch must build cleanly with W=1.
>>> Otherwise doing git bisections is a miserable experience.
>>> --
>>
>> As we mentioned in cover letter we have dependency with SOC patch.
>>
>> "These patches have a dependency on an SOC patch, which we are including at the
>> end of this series for reference. The SOC patch has been submitted in a separate
>> thread [2] and we are awaiting for it to be merged."
>>
>> SOC patch need to be applied prior applying the "net" patches. We have changed
>> the
>> order and appended the SOC patch at the end, because SOC changes need to go into
>> linux-next but not into net-next.
>>
>> We have make sure every individual patch has compiled successfully with W=1 if
>> we
>> apply SOC patch prior to the "net" patches.
>>
>
> If there is any dependency in the series, the pre-requisite patch should
> come before the dependent patch. In this series, SoC Patch should have
> been the patch 1/10 and the warnings could have been avoided.
>
Sure, we will change the order and resubmit the patches in the next version.
Thanks and Regards,
Parvathi.
Powered by blists - more mailing lists