[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5696365.DvuYhMxLoT@jernej-laptop>
Date: Fri, 04 Aug 2023 16:39:41 +0200
From: Jernej Škrabec <jernej.skrabec@...il.com>
To: John Watts <contact@...kia.org>
Cc: linux-sunxi@...ts.linux.dev, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Chen-Yu Tsai <wens@...e.org>,
Samuel Holland <samuel@...lland.org>,
Cristian Ciocaltea <cristian.ciocaltea@...labora.com>,
Maksim Kiselev <bigunclemax@...il.com>,
devicetree@...r.kernel.org, linux-riscv@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
mkl@...gutronix.de
Subject: Re: [PATCH] riscv: dts: allwinner: d1: Specify default CAN pins
Dne petek, 04. avgust 2023 ob 08:25:42 CEST je John Watts napisal(a):
> On Thu, Aug 03, 2023 at 10:59:30PM +0200, Jernej Škrabec wrote:
> > pinctrl-names and pinctrl-0 are usually at the top. However, since there
> > is no hard rule (I've seen it mixed), I'm fine with it.
>
> Happy to change if needed.
If you don't mind, please do.
>
> > Since original DT node entry goes through netdev tree, this should be
> > picked there or it can be dropped there and I pick both patches or I can
> > pick patch for later kernel version.
>
> Do I have to do something based on this, like resend my patch?
Nothing on your side.
Marc, since you took original patch through netdev tree, what is your decision
here?
Best regards,
Jernej
>
> > Best regards,
> > Jernej
>
> John
Powered by blists - more mailing lists