From: Krzysztof Kozlowski <krzk@kernel.org>
To: Donald Shannon <donalds@nvidia.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org
Subject: Re: [PATCH v7 0/2] Adding device tree and binding for NVIDIA GB200-UT3.0b
Date: Wed, 6 Aug 2025 08:12:03 +0200 [thread overview]
Message-ID: <63cfaf2c-a25a-45af-8f76-5352e6adf2f0@kernel.org> (raw)
In-Reply-To: <5e5c8bd2-4c4b-4371-a6b2-d4d4359a4233@nvidia.com>
On 05/08/2025 20:18, Donald Shannon wrote:
>>> Changes v6 -> v7:
>>> - Removed Acked-by Krzysztof
>> Why? You did not even give me chance to respond to your reply.
>>
>> Best regards,
>> Krzysztof
>
> Hi Krzysztof,
>
> I will reply here to keep our discussion together.
>
> I think that the issue was me using your kernel.org email and not your linaro.org email.
> I will fix this in the next patch series along with some fixes for the warnings from the other thread.
You should not "use email" at all. You MUST copy the tag as given,
without modifying it or writing by yourself. Use for example `b4
trailers` for that. Or just copy paste.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-06 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 22:23 [PATCH v7 0/2] Adding device tree and binding for NVIDIA GB200-UT3.0b Donald Shannon
2025-07-23 22:23 ` [PATCH v7 1/2] dt-bindings: arm: aspeed: Add NVIDIA GB200-UT3.0b board Donald Shannon
2025-07-24 7:54 ` Krzysztof Kozlowski
2025-07-23 22:23 ` [PATCH v7 2/2] ARM: dts: aspeed: Add NVIDIA GB200 UT3.0b board Donald Shannon
2025-07-24 7:54 ` [PATCH v7 0/2] Adding device tree and binding for NVIDIA GB200-UT3.0b Krzysztof Kozlowski
2025-08-05 18:18 ` Donald Shannon
2025-08-06 6:12 ` Krzysztof Kozlowski [this message]
2025-07-25 3:19 ` Rob Herring (Arm)
2025-07-25 3:25 ` Rob Herring
2025-07-31 2:11 ` 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=63cfaf2c-a25a-45af-8f76-5352e6adf2f0@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=donalds@nvidia.com \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh@kernel.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).