[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a1b84760-821f-a279-ca2c-b22d5f1a99fa@microchip.com>
Date: Mon, 27 Jun 2022 11:17:39 +0000
From: <Conor.Dooley@...rochip.com>
To: <mkl@...gutronix.de>
CC: <netdev@...r.kernel.org>, <davem@...emloft.net>, <kuba@...nel.org>,
<linux-can@...r.kernel.org>, <kernel@...gutronix.de>,
<palmer@...belt.com>, <linux-riscv@...ts.infradead.org>
Subject: Re: [PATCH net-next 16/22] riscv: dts: microchip: add mpfs's CAN
controllers
On 27/06/2022 08:30, Marc Kleine-Budde wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> On 27.06.2022 07:12:47, Conor.Dooley@...rochip.com wrote:
>> On 25/06/2022 13:03, Marc Kleine-Budde wrote:
>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>>
>>> From: Conor Dooley <conor.dooley@...rochip.com>
>>>
>>> PolarFire SoC has a pair of CAN controllers, but as they were
>>> undocumented there were omitted from the device tree. Add them.
>>>
>>> Link: https://lore.kernel.org/all/20220607065459.2035746-3-conor.dooley@microchip.com
>>> Signed-off-by: Conor Dooley <conor.dooley@...rochip.com>
>>> Signed-off-by: Marc Kleine-Budde <mkl@...gutronix.de>
>>
>> Hey Marc,
>> Not entirely familiar with the process here.
>> Do I apply this patch when the rest of the series gets taken,
>> or will this patch go through the net tree?
>
> Both patches:
>
> 38a71fc04895 riscv: dts: microchip: add mpfs's CAN controllers
> c878d518d7b6 dt-bindings: can: mpfs: document the mpfs CAN controller
>
> are on they way to mainline via the net-next tree. No further actions
> needed on your side.
dts through the netdev tree rater than via the arch? Seems a little odd,
but it'd be via my tree anyway and I don't mind & unless Palmer objects:
Acked-by: Conor Dooley <conor.dooley@...rochip.com>
Powered by blists - more mailing lists