From: Krzysztof Kozlowski <krzk@kernel.org>
To: William Kennington <william@wkennington.com>
Cc: Avi Fishman <avifishman70@gmail.com>,
Tomer Maimon <tmaimon77@gmail.com>,
Tali Perry <tali.perry1@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
openbmc@lists.ozlabs.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: nuvoton: Add USB Hosts
Date: Sun, 27 Apr 2025 21:10:09 +0200 [thread overview]
Message-ID: <d11e00b3-45ea-4eb5-8ac5-54c051b32a81@kernel.org> (raw)
In-Reply-To: <CAD_4BXgO3F0JVKQTAZxLXjPXHv4Rgf2Cz+Cm0PMzLDTx5C56tg@mail.gmail.com>
On 25/04/2025 23:18, William Kennington wrote:
> On Tue, Apr 15, 2025 at 11:52 PM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On 16/04/2025 02:18, William A. Kennington III wrote:
>>> The npcm 8xx chip has 2 EHCI and 2 OHCI hosts with driver support
>>> already existing in the kernel.
>>>
>>> Signed-off-by: William A. Kennington III <william@wkennington.com>
>>> ---
>>> .../dts/nuvoton/nuvoton-common-npcm8xx.dtsi | 28 +++++++++++++++++++
>>
>> Please do not send 10 separate patches, but one patchset for given
>> subsystem.
>
> When I send a patchset should I add the reply-to tags for all of these
> previous reviews? Or just resend as a new review?
I don't understand what you are asking me. You NEVER add manually
in-reply to. You should use either git send-email or b4 or patman.
Nothing else, no manual edits, no weird headers.
If you ask about review, that's entirely different topic - see
submitting patches. BTW, kernel docs also explain how to actually send
these emails...
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-04-27 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 0:18 [PATCH] arm64: dts: nuvoton: Add USB Hosts William A. Kennington III
2025-04-16 6:52 ` Krzysztof Kozlowski
2025-04-16 8:10 ` Tomer Maimon
2025-04-25 21:18 ` William Kennington
2025-04-27 19:10 ` Krzysztof Kozlowski [this message]
2025-05-07 2:58 ` Andrew Jeffery
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=d11e00b3-45ea-4eb5-8ac5-54c051b32a81@kernel.org \
--to=krzk@kernel.org \
--cc=avifishman70@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=william@wkennington.com \
/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