mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Peng Fan <peng.fan@nxp.com>, Shawn Guo <shawnguo@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>
Subject: Re: [PATCH 1/3] arm64: dts: freescale: use defines for interrupts
Date: Thu, 6 Jun 2024 08:14:36 +0200	[thread overview]
Message-ID: <6b7950ec-d513-410d-8652-30aab5a30207@linaro.org> (raw)
In-Reply-To: <AM6PR04MB594144EE748C5F61F72B63F688FA2@AM6PR04MB5941.eurprd04.prod.outlook.com>

On 06/06/2024 03:36, Peng Fan wrote:
>> Subject: [PATCH 1/3] arm64: dts: freescale: use defines for interrupts
>>
>> Replace hard-coded interrupt parts (GIC, flags) with standard defines for
>> readability.  No changes in resulting DTBs.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> 
> Reviewed-by: Peng Fan <peng.fan@nxp.com>

Please trim your answers, so we do not have to scroll needlessly through
entire email to see if you left some feedback or not.

Best regards,
Krzysztof


  reply	other threads:[~2024-06-06  6:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 15:30 Krzysztof Kozlowski
2024-06-05 15:30 ` [PATCH 2/3] arm64: dts: ls208xa: use defines for timer interrupts Krzysztof Kozlowski
2024-06-06  1:35   ` Peng Fan
2024-06-05 15:30 ` [PATCH 3/3] arm64: dts: imx8: use defines for interrupts Krzysztof Kozlowski
2024-06-06  1:35   ` Peng Fan
2024-06-06  1:36 ` [PATCH 1/3] arm64: dts: freescale: " Peng Fan
2024-06-06  6:14   ` Krzysztof Kozlowski [this message]
2024-06-17  1:20 ` 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=6b7950ec-d513-410d-8652-30aab5a30207@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®