From: Shawn Guo <shawnguo@kernel.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: frank.li@nxp.com, corbet@lwn.net, s.hauer@pengutronix.de,
kernel@pengutronix.de, will@kernel.org, mark.rutland@arm.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
festevam@gmail.com, conor+dt@kernel.org, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 5/5] arm64: dts: imx8dxl-ss-ddr: change ddr_pmu0 compatible
Date: Wed, 6 Dec 2023 09:34:21 +0800 [thread overview]
Message-ID: <20231206013421.GZ236001@dragon> (raw)
In-Reply-To: <20231120093317.2652866-5-xu.yang_2@nxp.com>
On Mon, Nov 20, 2023 at 05:33:17PM +0800, Xu Yang wrote:
> i.MX8DXL's ddr pmu has port/channel filter capabilities, but it still is
> compatible with "fsl,imx8-ddr-pmu". This will change the compatible.
>
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
Applied, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: frank.li@nxp.com, corbet@lwn.net, s.hauer@pengutronix.de,
kernel@pengutronix.de, will@kernel.org, mark.rutland@arm.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
festevam@gmail.com, conor+dt@kernel.org, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 5/5] arm64: dts: imx8dxl-ss-ddr: change ddr_pmu0 compatible
Date: Wed, 6 Dec 2023 09:34:21 +0800 [thread overview]
Message-ID: <20231206013421.GZ236001@dragon> (raw)
In-Reply-To: <20231120093317.2652866-5-xu.yang_2@nxp.com>
On Mon, Nov 20, 2023 at 05:33:17PM +0800, Xu Yang wrote:
> i.MX8DXL's ddr pmu has port/channel filter capabilities, but it still is
> compatible with "fsl,imx8-ddr-pmu". This will change the compatible.
>
> Signed-off-by: Xu Yang <xu.yang_2@nxp.com>
Applied, thanks!
_______________________________________________
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-12-06 1:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 9:33 [PATCH v3 1/5] perf: fsl_imx8_ddr: Add AXI ID PORT CHANNEL filter support Xu Yang
2023-11-20 9:33 ` Xu Yang
2023-11-20 9:33 ` [PATCH v3 2/5] docs/perf: Add explanation for DDR_CAP_AXI_ID_PORT_CHANNEL_FILTER quirk Xu Yang
2023-11-20 9:33 ` Xu Yang
2023-11-20 9:33 ` [PATCH v3 3/5] dt-bindings: perf: fsl-imx-ddr: Add i.MX8DXL compatible Xu Yang
2023-11-20 9:33 ` Xu Yang
2023-11-20 9:33 ` [PATCH v3 4/5] perf: fsl_imx8_ddr: Add driver support for i.MX8DXL DDR Perf Xu Yang
2023-11-20 9:33 ` Xu Yang
2023-11-20 9:33 ` [PATCH v3 5/5] arm64: dts: imx8dxl-ss-ddr: change ddr_pmu0 compatible Xu Yang
2023-11-20 9:33 ` Xu Yang
2023-12-06 1:34 ` Shawn Guo [this message]
2023-12-06 1:34 ` Shawn Guo
2023-12-05 15:16 ` [PATCH v3 1/5] perf: fsl_imx8_ddr: Add AXI ID PORT CHANNEL filter support Will Deacon
2023-12-05 15:16 ` Will Deacon
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=20231206013421.GZ236001@dragon \
--to=shawnguo@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=will@kernel.org \
--cc=xu.yang_2@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 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.