All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Matt Ranostay <mranostay@ti.com>
Cc: nm@ti.com, vigneshr@ti.com, krzysztof.kozlowski+dt@linaro.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: mfd: ti,j721e-system-controller: add compatible strings for other platforms
Date: Thu, 20 Oct 2022 09:24:51 -0500	[thread overview]
Message-ID: <20221020142451.GA1264860-robh@kernel.org> (raw)
In-Reply-To: <20221020032802.308545-2-mranostay@ti.com>

On Wed, Oct 19, 2022 at 08:28:01PM -0700, Matt Ranostay wrote:
> There are multiple J7 based platforms, and the j721e-system-controller
> shouldn't be define in non-j721e devices device trees.
> 
> This is mainly for clarity; but also useful in case there are future
> erratas that need to be fixed for a specific platform.
> 
> Signed-off-by: Matt Ranostay <mranostay@ti.com>
> ---
>  .../devicetree/bindings/mfd/ti,j721e-system-controller.yaml     | 2 ++
>  1 file changed, 2 insertions(+)

Use get_maintainers.pl if you want this applied (by Lee).

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Matt Ranostay <mranostay@ti.com>
Cc: nm@ti.com, vigneshr@ti.com, krzysztof.kozlowski+dt@linaro.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: mfd: ti,j721e-system-controller: add compatible strings for other platforms
Date: Thu, 20 Oct 2022 09:24:51 -0500	[thread overview]
Message-ID: <20221020142451.GA1264860-robh@kernel.org> (raw)
In-Reply-To: <20221020032802.308545-2-mranostay@ti.com>

On Wed, Oct 19, 2022 at 08:28:01PM -0700, Matt Ranostay wrote:
> There are multiple J7 based platforms, and the j721e-system-controller
> shouldn't be define in non-j721e devices device trees.
> 
> This is mainly for clarity; but also useful in case there are future
> erratas that need to be fixed for a specific platform.
> 
> Signed-off-by: Matt Ranostay <mranostay@ti.com>
> ---
>  .../devicetree/bindings/mfd/ti,j721e-system-controller.yaml     | 2 ++
>  1 file changed, 2 insertions(+)

Use get_maintainers.pl if you want this applied (by Lee).

  parent reply	other threads:[~2022-10-20 14:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20  3:28 [PATCH v2 0/2] arm64: dts: add new compatibles for J7 platforms Matt Ranostay
2022-10-20  3:28 ` Matt Ranostay
2022-10-20  3:28 ` [PATCH v2 1/2] dt-bindings: mfd: ti,j721e-system-controller: add compatible strings for other platforms Matt Ranostay
2022-10-20  3:28   ` Matt Ranostay
2022-10-20 13:49   ` Krzysztof Kozlowski
2022-10-20 13:49     ` Krzysztof Kozlowski
2022-10-20 14:24   ` Rob Herring [this message]
2022-10-20 14:24     ` Rob Herring
2022-10-20  3:28 ` [PATCH v2 2/2] arm64: dts: k3-j72*: correct compatible for syscon entries Matt Ranostay
2022-10-20  3:28   ` Matt Ranostay
2022-10-20 13:49   ` Krzysztof Kozlowski
2022-10-20 13:49     ` 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=20221020142451.GA1264860-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mranostay@ti.com \
    --cc=nm@ti.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.