From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Brad Griffis <bgriffis@nvidia.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Jon Hunter <jonathanh@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>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] arm64: tegra: Fix Tegra234 PCIe interrupt-map
Date: Sat, 14 Dec 2024 11:27:18 +0100 [thread overview]
Message-ID: <df097900-e6a9-44f0-8589-402ff50ed80b@linaro.org> (raw)
In-Reply-To: <8a372dab-ab8f-4635-a5ff-bd7c8ed4756d@nvidia.com>
On 14/12/2024 01:35, Brad Griffis wrote:
> On 12/13/24 05:26, Krzysztof Kozlowski wrote:
>> Yeah, that was just an assumption, but three independent people are
>> Ccing address which does not exist in the kernel and it is impossible to
>> get/deduce/invent. Three patchsets from three different people...
>>
>> Best regards,
>> Krzysztof
>
> I am developing and testing on mainline. However, when I checked the
> get_maintainer.pl output on first glance it looked unchanged and I
> copied/pasted an old "git send-email" command that had the older email
> address.
You should not "cache" the output of get_maintainers.pl EVER. Addresses
change, people are added or removed. Just use b4 or simple
scripts/aliases (like Rob's send email identity or
https://github.com/krzk/tools/blob/master/linux/.bash_aliases_linux#L92 ).
Best regards,
Krzysztof
prev parent reply other threads:[~2024-12-14 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 21:11 [PATCH] arm64: tegra: Fix Tegra234 PCIe interrupt-map Brad Griffis
2024-12-13 9:51 ` Jon Hunter
2024-12-13 10:21 ` Thierry Reding
2024-12-13 11:11 ` Krzysztof Kozlowski
2024-12-13 11:37 ` Jon Hunter
2024-12-13 13:26 ` Krzysztof Kozlowski
2024-12-14 0:35 ` Brad Griffis
2024-12-14 10:27 ` Krzysztof Kozlowski [this message]
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=df097900-e6a9-44f0-8589-402ff50ed80b@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=krzk@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.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