From: Brad Griffis <bgriffis@nvidia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
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: Fri, 13 Dec 2024 16:35:01 -0800 [thread overview]
Message-ID: <8a372dab-ab8f-4635-a5ff-bd7c8ed4756d@nvidia.com> (raw)
In-Reply-To: <ac09839a-b356-489c-9ab9-54a567fdcf95@kernel.org>
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.
And you are probably getting multiple of them due to me "helping" other
people by sharing some of the commands/syntax.
I apologize for the mistake. I will check that more carefully from now
on. I sent out v2 and made sure to get this correct!
next prev parent reply other threads:[~2024-12-14 0:35 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 [this message]
2024-12-14 10:27 ` Krzysztof Kozlowski
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=8a372dab-ab8f-4635-a5ff-bd7c8ed4756d@nvidia.com \
--to=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=krzysztof.kozlowski@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.