devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, netdev@vger.kernel.org,
	devicetree@vger.kernel.org, vbhadram@nvidia.com,
	treding@nvidia.com, robh+dt@kernel.org, catalin.marinas@arm.com,
	krzysztof.kozlowski+dt@linaro.org, kuba@kernel.org,
	jonathanh@nvidia.com, will@kernel.org
Subject: Re: (subset) [PATCH net-next v1 4/9] memory: tegra: Add MGBE memory clients for Tegra234
Date: Sat, 25 Jun 2022 22:17:24 +0200	[thread overview]
Message-ID: <000ca74c-16e1-754b-3398-8c9a65faee0b@linaro.org> (raw)
In-Reply-To: <YrXlQJ1qzsZZrx7Q@orome>

On 24/06/2022 18:24, Thierry Reding wrote:
> On Fri, Jun 24, 2022 at 06:06:35PM +0200, Krzysztof Kozlowski wrote:
>> On Thu, 23 Jun 2022 13:16:10 +0530, Bhadram Varka wrote:
>>> From: Thierry Reding <treding@nvidia.com>
>>>
>>> Tegra234 has multiple network interfaces with each their own memory
>>> clients and stream IDs to allow for proper isolation.
>>>
>>>
>>
>> Applied, thanks!
>>
>> [4/9] memory: tegra: Add MGBE memory clients for Tegra234
>>       https://git.kernel.org/krzk/linux-mem-ctrl/c/6b36629c85dc7d4551e57e92a3e970d099333e4e
> 
> Ah yes, you'll need the dt-bindings header for this driver bit as well.
> If you don't mind I could pick all of these up into the Tegra tree and
> resolve the dependencies there, then send a pull request for the memory
> tree that incorporates the dt-bindings branch as a dependency.
> 
> That way you don't have to worry about this at all. We might also get
> another set of similar changes for PCI or USB during this cycle, so it'd
> certainly be easier to collect all of these in a central place.

I cannot take DTS patches to the driver tree, so it's easier if you take
it and handle the dependencies.

Best regards,
Krzysztof

  reply	other threads:[~2022-06-25 20:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  7:46 [PATCH net-next v1 1/9] dt-bindings: power: Add Tegra234 MGBE power domains Bhadram Varka
2022-06-23  7:46 ` [PATCH net-next v1 2/9] dt-bindings: Add Tegra234 MGBE clocks and resets Bhadram Varka
2022-06-24 16:02   ` Krzysztof Kozlowski
2022-06-24 16:21     ` Thierry Reding
2022-06-24 17:12       ` Krzysztof Kozlowski
2022-06-23  7:46 ` [PATCH net-next v1 3/9] dt-bindings: memory: Add Tegra234 MGBE memory clients Bhadram Varka
2022-06-24 16:06   ` (subset) " Krzysztof Kozlowski
2022-06-24 16:10     ` Krzysztof Kozlowski
2022-06-24 16:19       ` Thierry Reding
2022-06-25 20:18   ` Krzysztof Kozlowski
2022-06-23  7:46 ` [PATCH net-next v1 4/9] memory: tegra: Add MGBE memory clients for Tegra234 Bhadram Varka
2022-06-24 16:06   ` (subset) " Krzysztof Kozlowski
2022-06-24 16:24     ` Thierry Reding
2022-06-25 20:17       ` Krzysztof Kozlowski [this message]
2022-06-25 20:18   ` Krzysztof Kozlowski
2022-06-23  7:46 ` [PATCH net-next v1 5/9] dt-bindings: net: Add Tegra234 MGBE Bhadram Varka
2022-06-28 19:55   ` Rob Herring
2022-06-30 14:54     ` Thierry Reding
2022-07-07  4:10       ` Bhadram Varka
2022-06-23  7:46 ` [PATCH net-next v1 6/9] arm64: tegra: Add MGBE nodes on Tegra234 Bhadram Varka
2022-06-23  7:46 ` [PATCH net-next v1 7/9] arm64: tegra: Enable MGBE on Jetson AGX Orin Developer Kit Bhadram Varka
2022-06-23  7:46 ` [PATCH net-next v1 8/9] stmmac: tegra: Add MGBE support Bhadram Varka
2022-06-24 18:16   ` Jakub Kicinski
2022-06-23  7:46 ` [PATCH net-next v1 9/9] arm64: defconfig: Enable Tegra MGBE driver Bhadram Varka
2022-06-24 16:02 ` [PATCH net-next v1 1/9] dt-bindings: power: Add Tegra234 MGBE power domains Krzysztof Kozlowski

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=000ca74c-16e1-754b-3398-8c9a65faee0b@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=thierry.reding@gmail.com \
    --cc=treding@nvidia.com \
    --cc=vbhadram@nvidia.com \
    --cc=will@kernel.org \
    /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).