Message ID | 20250214054702.1073139-1-parvathi@couthit.com (mailing list archive) |
---|---|
Headers | show |
Series | PRU-ICSSM Ethernet Driver | expand |
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.
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. Thanks and Regards, Parvathi.
On Tue, 18 Feb 2025 15:36:20 +0530 (IST) Parvathi Pudi wrote: > > 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. Please resubmit after the merge window.