From: Jakub Kicinski <kuba@kernel.org>
To: MD Danish Anwar <danishanwar@ti.com>
Cc: nm@ti.com, andrew@lunn.ch, Paolo Abeni <pabeni@redhat.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, YueHaibing <yuehaibing@huawei.com>,
srk@ti.com, "Andrew F. Davis" <afd@ti.com>,
Roger Quadros <rogerq@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
ssantosh@kernel.org, netdev@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5 0/2] Introduce ICSSG based ethernet Driver
Date: Fri, 10 Feb 2023 16:38:16 -0800 [thread overview]
Message-ID: <20230210163816.423a0ee9@kernel.org> (raw)
In-Reply-To: <20230210114957.2667963-1-danishanwar@ti.com>
On Fri, 10 Feb 2023 17:19:55 +0530 MD Danish Anwar wrote:
> This series depends on two patch series that are not yet merged, one in
> the remoteproc tree and another in the soc tree. the first one is titled
> Introduce PRU remoteproc consumer API and the second one is titled
> Introduce PRU platform consumer API.
> Both of these are required for this driver.
>
> To explain this dependency and to get reviews, I had earlier posted all
> three of these as an RFC[1], this can be seen for understanding the
> dependencies.
And please continue to post them as RFC :( If there are dependencies
which the networking tree doesn't have we can't possibly merge these :(
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-11 0:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 11:49 [PATCH v5 0/2] Introduce ICSSG based ethernet Driver MD Danish Anwar
2023-02-10 11:49 ` [PATCH v5 1/2] dt-bindings: net: Add ICSSG Ethernet MD Danish Anwar
2023-02-10 13:58 ` Rob Herring
2023-02-10 15:30 ` [EXTERNAL] " Md Danish Anwar
2023-02-10 18:37 ` Rob Herring
2023-02-10 19:20 ` Rob Herring
2023-03-07 4:57 ` [EXTERNAL] " Md Danish Anwar
2023-03-07 8:58 ` Krzysztof Kozlowski
2023-03-09 11:44 ` Md Danish Anwar
2023-03-09 12:53 ` Krzysztof Kozlowski
2023-02-11 0:38 ` Jakub Kicinski [this message]
2023-03-07 5:00 ` [EXTERNAL] Re: [PATCH v5 0/2] Introduce ICSSG based ethernet Driver Md Danish Anwar
[not found] ` <20230210114957.2667963-3-danishanwar@ti.com>
2023-02-11 15:29 ` [PATCH v5 2/2] net: ti: icssg-prueth: Add ICSSG ethernet driver Andrew Lunn
2023-03-21 8:51 ` [PATCH v5 0/2] Introduce ICSSG based ethernet Driver Christian Gmeiner
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=20230210163816.423a0ee9@kernel.org \
--to=kuba@kernel.org \
--cc=afd@ti.com \
--cc=andrew@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@kernel.org \
--cc=srk@ti.com \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.com \
--cc=yuehaibing@huawei.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).