From: Jakub Kicinski <kuba@kernel.org>
To: Parvathi Pudi <parvathi@couthit.com>
Cc: danishanwar <danishanwar@ti.com>, rogerq <rogerq@kernel.org>,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, nm@ti.com, ssantosh@kernel.org,
richardcochran@gmail.com, basharath <basharath@couthit.com>,
schnelle@linux.ibm.com, diogo ivo <diogo.ivo@siemens.com>,
m-karicheri2@ti.com, horms@kernel.org,
jacob e keller <jacob.e.keller@intel.com>,
m-malladi@ti.com,
javier carrasco cruz <javier.carrasco.cruz@gmail.com>,
afd@ti.com, s-anna@ti.com, linux-arm-kernel@lists.infradead.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, pratheesh <pratheesh@ti.com>,
Prajith Jayarajan <prajith@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
praneeth@ti.com, srk@ti.com, rogerq@ti.com,
krishna <krishna@couthit.com>, pmohan <pmohan@couthit.com>,
mohan <mohan@couthit.com>
Subject: Re: [PATCH net-next v3 00/10] PRU-ICSSM Ethernet Driver
Date: Tue, 18 Feb 2025 06:40:08 -0800 [thread overview]
Message-ID: <20250218064008.762e9b94@kernel.org> (raw)
In-Reply-To: <1348929889.600853.1739873180072.JavaMail.zimbra@couthit.local>
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.
next prev parent reply other threads:[~2025-02-18 14:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 5:46 [PATCH net-next v3 00/10] PRU-ICSSM Ethernet Driver parvathi
2025-02-14 5:46 ` [PATCH net-next v3 01/10] dt-bindings: net: ti: Adds DUAL-EMAC mode support on PRU-ICSS2 for AM57xx SOCs parvathi
2025-02-19 22:51 ` Rob Herring
2025-02-21 12:32 ` Parvathi Pudi
2025-02-14 5:46 ` [PATCH net-next v3 02/10] net: ti: prueth: Adds ICSSM Ethernet driver parvathi
2025-02-20 9:19 ` Ratheesh Kannoth
2025-02-21 12:35 ` Parvathi Pudi
2025-02-14 5:46 ` [PATCH net-next v3 03/10] net: ti: prueth: Adds PRUETH HW and SW configuration parvathi
2025-02-14 7:37 ` [PATCH net-next v3 04/10] net: ti: prueth: Adds link detection, RX and TX support parvathi
2025-02-14 15:44 ` Maxime Chevallier
2025-02-18 9:58 ` Parvathi Pudi
2025-02-14 7:37 ` [PATCH net-next v3 05/10] net: ti: prueth: Adds ethtool support for ICSSM PRUETH Driver parvathi
2025-02-14 7:37 ` [PATCH net-next v3 06/10] net: ti: prueth: Adds HW timestamping support for PTP using PRU-ICSS IEP module parvathi
2025-02-14 7:37 ` [PATCH net-next v3 07/10] net: ti: prueth: Adds support for network filters for traffic control supported by PRU-ICSS parvathi
2025-02-14 8:53 ` [PATCH net-next v3 08/10] net: ti: prueth: Adds support for RX interrupt coalescing/pacing parvathi
2025-02-14 8:53 ` [PATCH net-next v3 09/10] net: ti: prueth: Adds power management support for PRU-ICSS parvathi
2025-02-14 8:53 ` [PATCH net-next v3 10/10] soc: ti: PRUSS OCP configuration parvathi
2025-02-15 1:02 ` [PATCH net-next v3 00/10] PRU-ICSSM Ethernet Driver Jakub Kicinski
2025-02-18 10:06 ` Parvathi Pudi
2025-02-18 14:40 ` Jakub Kicinski [this message]
2025-02-24 6:56 ` MD Danish Anwar
2025-02-28 10:55 ` Parvathi Pudi
2025-02-26 18:44 ` Nishanth Menon
2025-02-28 10:58 ` Parvathi Pudi
2025-03-06 13:43 ` Parvathi Pudi
2025-03-07 19:47 ` Nishanth Menon
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=20250218064008.762e9b94@kernel.org \
--to=kuba@kernel.org \
--cc=afd@ti.com \
--cc=andrew+netdev@lunn.ch \
--cc=basharath@couthit.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=diogo.ivo@siemens.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=krishna@couthit.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=m-malladi@ti.com \
--cc=mohan@couthit.com \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=pabeni@redhat.com \
--cc=parvathi@couthit.com \
--cc=pmohan@couthit.com \
--cc=prajith@ti.com \
--cc=praneeth@ti.com \
--cc=pratheesh@ti.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=rogerq@ti.com \
--cc=s-anna@ti.com \
--cc=schnelle@linux.ibm.com \
--cc=srk@ti.com \
--cc=ssantosh@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).