From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ivy Huang <yijuh@nvidia.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
Brad Griffis <bgriffis@nvidia.com>
Cc: Sumit Gupta <sumitg@nvidia.com>
Subject: Re: [PATCH 1/2] arm64: tegra: fix typo in Tegra234 dce-fabric compatible
Date: Fri, 13 Dec 2024 12:10:06 +0100 [thread overview]
Message-ID: <ffd6ec4e-61a6-4713-8be2-20d06ae5b448@linaro.org> (raw)
In-Reply-To: <20241213000305.3533971-2-yijuh@nvidia.com>
On 13/12/2024 01:03, Ivy Huang wrote:
> From: Sumit Gupta <sumitg@nvidia.com>
>
> Fix typo in the compatible string of Tegra234 dce-fabric.
In what way fix? How does it affect users?
Why no fixes tag?
You CC-ed an address, which suggests you do not work on mainline kernel
or you do not use get_maintainers.pl/b4/patman. Please rebase and always
work on mainline or start using mentioned tools, so correct addresses
will be used.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-12-13 11:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 0:03 [PATCH 0/2] Tegra234 fabric fixes Ivy Huang
2024-12-13 0:03 ` [PATCH 1/2] arm64: tegra: fix typo in Tegra234 dce-fabric compatible Ivy Huang
2024-12-13 2:32 ` Brad Griffis
2024-12-13 9:44 ` Jon Hunter
2024-12-13 10:22 ` Thierry Reding
2024-12-13 11:11 ` Krzysztof Kozlowski
2024-12-13 11:10 ` Krzysztof Kozlowski [this message]
2024-12-18 2:08 ` Brad Griffis
2024-12-13 0:03 ` [PATCH 2/2] arm64: tegra: disable Tegra234 sce-fabric node Ivy Huang
2024-12-13 2:32 ` Brad Griffis
2024-12-13 9:45 ` Jon Hunter
2024-12-13 10:28 ` Thierry Reding
2024-12-14 0:39 ` Brad Griffis
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=ffd6ec4e-61a6-4713-8be2-20d06ae5b448@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bgriffis@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sumitg@nvidia.com \
--cc=thierry.reding@gmail.com \
--cc=yijuh@nvidia.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