public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: John Watts <contact@jookia.org>
To: "Jernej Škrabec" <jernej.skrabec@gmail.com>
Cc: devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Samuel Holland <samuel@sholland.org>,
	linux-kernel@vger.kernel.org, Chen-Yu Tsai <wens@csie.org>,
	Rob Herring <robh+dt@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Maksim Kiselev <bigunclemax@gmail.com>,
	linux-riscv@lists.infradead.org, mkl@pengutronix.de,
	linux-sunxi@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] riscv: dts: allwinner: d1: Specify default CAN pins
Date: Fri, 4 Aug 2023 16:25:42 +1000	[thread overview]
Message-ID: <ZMyZ5kZSiiJHtdeS@titan> (raw)
In-Reply-To: <3248110.44csPzL39Z@jernej-laptop>

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.

> 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?

> Best regards,
> Jernej

John

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2023-08-04  6:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31  2:36 [PATCH] riscv: dts: allwinner: d1: Specify default CAN pins John Watts
2023-08-03 20:54 ` Jernej Škrabec
2023-08-03 20:59 ` Jernej Škrabec
2023-08-04  6:25   ` John Watts [this message]
2023-08-04 14:39     ` Jernej Škrabec
2023-08-05 10:42       ` John Watts
2023-08-07  7:14       ` Marc Kleine-Budde
2023-08-13  4:13   ` Chen-Yu Tsai

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=ZMyZ5kZSiiJHtdeS@titan \
    --to=contact@jookia.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=bigunclemax@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=mkl@pengutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh+dt@kernel.org \
    --cc=samuel@sholland.org \
    --cc=wens@csie.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