From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "Jernej Škrabec" <jernej.skrabec@gmail.com>
Cc: John Watts <contact@jookia.org>,
linux-sunxi@lists.linux.dev, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Chen-Yu Tsai <wens@csie.org>,
Samuel Holland <samuel@sholland.org>,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
Maksim Kiselev <bigunclemax@gmail.com>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: dts: allwinner: d1: Specify default CAN pins
Date: Mon, 7 Aug 2023 09:14:38 +0200 [thread overview]
Message-ID: <20230807-leverage-manatee-687c46db39f8-mkl@pengutronix.de> (raw)
In-Reply-To: <5696365.DvuYhMxLoT@jernej-laptop>
[-- Attachment #1.1: Type: text/plain, Size: 1168 bytes --]
On 04.08.2023 16:39:41, Jernej Škrabec wrote:
> 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?
I'll take the DT patches though linux-can-next to net-next.
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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-07 7:15 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
2023-08-04 14:39 ` Jernej Škrabec
2023-08-05 10:42 ` John Watts
2023-08-07 7:14 ` Marc Kleine-Budde [this message]
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=20230807-leverage-manatee-687c46db39f8-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=aou@eecs.berkeley.edu \
--cc=bigunclemax@gmail.com \
--cc=conor+dt@kernel.org \
--cc=contact@jookia.org \
--cc=cristian.ciocaltea@collabora.com \
--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=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;
as well as URLs for NNTP newsgroup(s).