[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8552c377-b2e9-749a-9f0c-7c444fe012c6@ti.com>
Date: Fri, 14 Apr 2023 11:42:52 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: Judith Mendez <jm@...com>,
Chandrasekar Ramakrishnan <rcsekar@...sung.com>
CC: Nishanth Menon <nm@...com>, Andrew Davis <afd@...com>,
Wolfgang Grandegger <wg@...ndegger.com>,
Marc Kleine-Budde <mkl@...gutronix.de>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
<linux-can@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<devicetree@...r.kernel.org>, <netdev@...r.kernel.org>,
Schuyler Patton <spatton@...com>
Subject: Re: [RFC PATCH 0/5] Enable multiple MCAN on AM62x
Hi Judith,
On 14/04/23 04:00, Judith Mendez wrote:
> Judith Mendez (5):
> arm64: dts: ti: Add AM62x MCAN MAIN domain transceiver overlay
> arm64: defconfig: Enable MCAN driver
> dt-binding: can: m_can: Remove required interrupt attributes
> arm64: dts: ti: Enable multiple MCAN for AM62x in MCU MCAN overlay
> can: m_can: Add hrtimer to generate software interrupt
This is fine for RFC, but next time, please split DT and defconfig
changes (1/5,2/5, and 4/5) to separate series as they have to go via
arm64 tree.
--
Regards
Vignesh
Powered by blists - more mailing lists