From: Markus Elfring <Markus.Elfring@web.de>
To: Conor Dooley <conor@kernel.org>,
linux-can@vger.kernel.org, linux-sunxi@lists.linux.dev,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
kernel-janitors@vger.kernel.org, John Watts <contact@jookia.org>
Cc: Albert Ou <aou@eecs.berkeley.edu>, Chen-Yu Tsai <wens@csie.org>,
Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Maksim Kiselev <bigunclemax@gmail.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Rob Herring <robh+dt@kernel.org>,
Samuel Holland <samuel@sholland.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [v3] riscv: dts: allwinner: d1: Add CAN controller nodes
Date: Wed, 9 Aug 2023 08:10:34 +0200 [thread overview]
Message-ID: <23c9ff53-82f3-491a-91f7-131cba6c607d@web.de> (raw)
In-Reply-To: <20230808-swerve-tartly-07140c59539e@spud>
> Markus, please stop bothering developers with nuisance comments.
Why do you interpret a recurring patch review in such a direction?
How much do mentioned concerns hinder the integration of the discussed patch?
Regards,
Markus
_______________________________________________
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-09 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 19:19 [PATCH v3] riscv: dts: allwinner: d1: Add CAN controller nodes John Watts
2023-08-08 14:26 ` Markus Elfring
2023-08-08 14:32 ` Conor Dooley
2023-08-09 6:10 ` Markus Elfring [this message]
2023-08-08 14:36 ` Marc Kleine-Budde
2023-08-13 4:17 ` Chen-Yu Tsai
2023-08-13 4:23 ` John Watts
2023-08-13 6:14 ` Chen-Yu Tsai
2023-08-13 6:16 ` John Watts
2023-09-01 16:25 ` patchwork-bot+linux-riscv
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=23c9ff53-82f3-491a-91f7-131cba6c607d@web.de \
--to=markus.elfring@web.de \
--cc=aou@eecs.berkeley.edu \
--cc=bigunclemax@gmail.com \
--cc=conor@kernel.org \
--cc=contact@jookia.org \
--cc=cristian.ciocaltea@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.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