From: Tony Lindgren <tony@atomide.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Bartosz Golaszewski" <brgl@bgdev.pl>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: ti: split interrupts per cells
Date: Wed, 2 Aug 2023 11:21:29 +0300 [thread overview]
Message-ID: <20230802082129.GB14799@atomide.com> (raw)
In-Reply-To: <20230731060429.GC5194@atomide.com>
* Tony Lindgren <tony@atomide.com> [230731 06:04]:
> * Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> [230730 14:15]:
> > Each interrupt should be in its own cell. This is much more readable.
>
> Looks good to me, Bartosz care to ack this? I can apply this on top
> of v6.5-rc1 with the missing pinctrl single node name changes so you'll
> have a commit to merge in in case it's needed for merge conflicts.
Pushed out omap-for-v6.6/dt branch, seems to merge just fine with current
Linux next.
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Bartosz Golaszewski" <brgl@bgdev.pl>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: ti: split interrupts per cells
Date: Wed, 2 Aug 2023 11:21:29 +0300 [thread overview]
Message-ID: <20230802082129.GB14799@atomide.com> (raw)
In-Reply-To: <20230731060429.GC5194@atomide.com>
* Tony Lindgren <tony@atomide.com> [230731 06:04]:
> * Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> [230730 14:15]:
> > Each interrupt should be in its own cell. This is much more readable.
>
> Looks good to me, Bartosz care to ack this? I can apply this on top
> of v6.5-rc1 with the missing pinctrl single node name changes so you'll
> have a commit to merge in in case it's needed for merge conflicts.
Pushed out omap-for-v6.6/dt branch, seems to merge just fine with current
Linux next.
Regards,
Tony
_______________________________________________
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-08-02 8:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 11:15 [PATCH] ARM: dts: ti: split interrupts per cells Krzysztof Kozlowski
2023-07-30 11:15 ` Krzysztof Kozlowski
2023-07-31 6:04 ` Tony Lindgren
2023-07-31 6:04 ` Tony Lindgren
2023-08-02 8:21 ` Tony Lindgren [this message]
2023-08-02 8:21 ` Tony Lindgren
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=20230802082129.GB14799@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@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.