From: Shawn Guo <shawnguo2@yeah.net>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: haibo.chen@nxp.com, jic23@kernel.org, lars@metafoo.de,
robh@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 2/2] arm64: dts: imx93: drop the 4th interrupt for ADC
Date: Thu, 28 Mar 2024 20:47:58 +0800 [thread overview]
Message-ID: <ZgVm/g04jK+hTNAV@dragon> (raw)
In-Reply-To: <20240226130826.3824251-2-peng.fan@oss.nxp.com>
On Mon, Feb 26, 2024 at 09:08:26PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Per i.MX93 Reference Mannual Rev.4, 12/2023, there is no interrupt 268,
> drop it.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
Applied, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo2@yeah.net>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: haibo.chen@nxp.com, jic23@kernel.org, lars@metafoo.de,
robh@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 2/2] arm64: dts: imx93: drop the 4th interrupt for ADC
Date: Thu, 28 Mar 2024 20:47:58 +0800 [thread overview]
Message-ID: <ZgVm/g04jK+hTNAV@dragon> (raw)
In-Reply-To: <20240226130826.3824251-2-peng.fan@oss.nxp.com>
On Mon, Feb 26, 2024 at 09:08:26PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Per i.MX93 Reference Mannual Rev.4, 12/2023, there is no interrupt 268,
> drop it.
>
> Signed-off-by: Peng Fan <peng.fan@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:[~2024-03-28 12:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 13:08 [PATCH 1/2] dt-bindings: iio: adc: imx93: drop the 4th interrupt Peng Fan (OSS)
2024-02-26 13:08 ` Peng Fan (OSS)
2024-02-26 13:08 ` [PATCH 2/2] arm64: dts: imx93: drop the 4th interrupt for ADC Peng Fan (OSS)
2024-02-26 13:08 ` Peng Fan (OSS)
2024-03-15 1:01 ` Peng Fan
2024-03-15 1:01 ` Peng Fan
2024-03-28 12:47 ` Shawn Guo [this message]
2024-03-28 12:47 ` Shawn Guo
2024-02-26 16:24 ` [PATCH 1/2] dt-bindings: iio: adc: imx93: drop the 4th interrupt Conor Dooley
2024-02-26 16:24 ` Conor Dooley
2024-02-26 19:20 ` Jonathan Cameron
2024-02-26 19:20 ` Jonathan Cameron
2024-02-26 21:17 ` Conor Dooley
2024-02-26 21:17 ` Conor Dooley
2024-02-26 22:06 ` Jonathan Cameron
2024-02-26 22:06 ` Jonathan Cameron
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=ZgVm/g04jK+hTNAV@dragon \
--to=shawnguo2@yeah.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=jic23@kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 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.