devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sherry Sun <sherry.sun@nxp.com>,
	robh+dt@kernel.org, krzk+dt@kernel.org, shawnguo@kernel.org,
	s.hauer@pengutronix.de, manish.narani@xilinx.com,
	michal.simek@xilinx.com, dinguyen@kernel.org, bp@suse.de
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: Re: [PATCH V2 1/2] dt-bindings: memory: snps,ddrc-3.80a compatible also need interrupts
Date: Mon, 21 Mar 2022 09:10:49 +0100	[thread overview]
Message-ID: <3f9605e5-16e4-e982-73d6-ab116155d2d7@kernel.org> (raw)
In-Reply-To: <20220321075131.17811-2-sherry.sun@nxp.com>

On 21/03/2022 08:51, Sherry Sun wrote:
> For the snps,ddrc-3.80a compatible, the interrupts property is also
> required, also order the compatibles by name (s goes before x).
> 
> Signed-off-by: Sherry Sun <sherry.sun@nxp.com>
> ---
>  .../bindings/memory-controllers/synopsys,ddrc-ecc.yaml      | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 

Fixes: a9e6b3819b36 ("dt-bindings: memory: Add entry for version 3.80a")


Looks good, I will take it after merge window. Somehow I was not cc-ed
on previous memory controllers patch. :(

Best regards,
Krzysztof

  reply	other threads:[~2022-03-21  8:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21  7:51 [PATCH V2 0/2] add ddr controller node to support EDAC on imx8mp Sherry Sun
2022-03-21  7:51 ` [PATCH V2 1/2] dt-bindings: memory: snps,ddrc-3.80a compatible also need interrupts Sherry Sun
2022-03-21  8:10   ` Krzysztof Kozlowski [this message]
2022-04-04 17:08   ` (subset) " Krzysztof Kozlowski
2022-03-21  7:51 ` [PATCH V2 2/2] arm64: dts: imx8mp: add ddr controller node to support EDAC on imx8mp Sherry Sun
2022-03-21  8:09   ` Krzysztof Kozlowski
2022-04-10  1:34   ` Shawn Guo

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=3f9605e5-16e4-e982-73d6-ab116155d2d7@kernel.org \
    --to=krzk@kernel.org \
    --cc=bp@suse.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dinguyen@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manish.narani@xilinx.com \
    --cc=michal.simek@xilinx.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=sherry.sun@nxp.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).