From: Krzysztof Kozlowski <krzk@kernel.org>
To: John Watts <contact@jookia.org>
Cc: linux-sunxi@lists.linux.dev, devicetree@vger.kernel.org,
linux-can@vger.kernel.org, linux-riscv@lists.infradead.org,
Fabien Poussin <fabien.poussin@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Chen-Yu Tsai <wens@csie.org>
Subject: Re: [PATCH 2/4] riscv: dts: allwinner: d1: Add CAN controller nodes
Date: Mon, 17 Jul 2023 08:39:52 +0200 [thread overview]
Message-ID: <9cd339c0-5e96-beba-e567-0a18d11d06b4@kernel.org> (raw)
In-Reply-To: <ZLQf5AYOCT3EQXyC@titan>
On 16/07/2023 18:50, John Watts wrote:
> Hello,
>
> Thanks for spending your time replying to this.
>
> On Sun, Jul 16, 2023 at 06:35:17PM +0200, Krzysztof Kozlowski wrote:
>> On 15/07/2023 13:25, Jookia wrote:
>>> From: John Watts <contact@jookia.org>
>>>
>>> The Allwinner D1, T113 provide two CAN controllers that are variants
>>> of the R40 controller.
>>>
>>> I have tested support for these controllers on two boards:
>>>
>>
>> Please use scripts/get_maintainers.pl to get a list of necessary people
>> and lists to CC (and consider --no-git-fallback argument). It might
>> happen, that command when run on an older kernel, gives you outdated
>> entries. Therefore please be sure you base your patches on recent Linux
>> kernel.
>
> I ran this script and selected some of the emails and CCed them, at least I
So the others you skipped Like let's pick this maintainer, but skip the
others? This is not how does it work. You are expected to CC all
maintainers (and to clarify the obvious: maintainers, not random
contributors). Some maintainers explicitly agree to be skipped, but
where do you see such statement from me?
Best regards,
Krzysztof
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-07-17 6:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 11:25 [PATCH 0/4] Add support for Allwinner D1 CAN controllers Jookia
2023-07-15 11:25 ` [PATCH 1/4] dt-bindings: net: can: Add support for Allwinner D1 CAN controller Jookia
2023-07-15 11:25 ` [PATCH 2/4] riscv: dts: allwinner: d1: Add CAN controller nodes Jookia
2023-07-16 16:35 ` Krzysztof Kozlowski
2023-07-16 16:50 ` John Watts
2023-07-17 6:39 ` Krzysztof Kozlowski [this message]
2023-07-17 8:26 ` John Watts
2023-07-15 11:25 ` [PATCH 3/4] can: sun4i_can: Add send support for the Allwinner D1 Jookia
2023-07-16 16:36 ` Krzysztof Kozlowski
2023-07-16 16:52 ` John Watts
2023-07-17 6:41 ` Krzysztof Kozlowski
2023-07-17 7:03 ` Marc Kleine-Budde
2023-07-17 7:12 ` Krzysztof Kozlowski
2023-07-17 8:28 ` John Watts
2023-07-15 11:25 ` [PATCH 4/4] can: sun4i_can: Correctly set acceptance registers on the D1 Jookia
2023-07-16 16:45 ` Jernej Škrabec
2023-07-16 16:52 ` John Watts
2023-07-17 8:00 ` [PATCH 0/4] Add support for Allwinner D1 CAN controllers Ben Dooks
2023-07-17 8:27 ` John Watts
2023-07-18 22:15 ` Rob Herring
2023-07-18 22:38 ` Conor Dooley
2023-07-19 6:52 ` John Watts
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=9cd339c0-5e96-beba-e567-0a18d11d06b4@kernel.org \
--to=krzk@kernel.org \
--cc=contact@jookia.org \
--cc=devicetree@vger.kernel.org \
--cc=fabien.poussin@gmail.com \
--cc=jernej.skrabec@gmail.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--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).