From: Krzysztof Kozlowski <krzk@kernel.org>
To: David Heidelberg <david@ixit.cz>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alexander Martinz <amartinz@shift.eco>
Cc: Petr Hodina <petr.hodina@protonmail.com>,
biemster <l.j.beemster@gmail.com>,
netdev@vger.kernel.org, linux-arm-msm@vger.kernel.org,
oe-linux-nfc@lists.linux.dev, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] arm64: dts: qcom: sdm845-oneplus: Enable NFC
Date: Tue, 24 Mar 2026 10:38:43 +0100 [thread overview]
Message-ID: <f69eabea-f065-437d-ba09-614ead9228ec@kernel.org> (raw)
In-Reply-To: <42352c0c-7464-4e78-8f89-20bdf7abd988@ixit.cz>
On 24/03/2026 10:35, David Heidelberg wrote:
> On 24/03/2026 08:03, Krzysztof Kozlowski wrote:
>> On 24/03/2026 00:20, David Heidelberg via B4 Relay wrote:
>>> From: biemster <l.j.beemster@gmail.com>
>>>
>>> Enable NFC controller NXP PN553, which is part of the package NXP NQ330
>>> (NFC + eSE).
>>>
>>> Signed-off-by: biemster <l.j.beemster@gmail.com>
>>
>> Same comment as last time. We do not take anonymous contributions.
>
> > then you just add a line saying:
> >
> > Signed-off-by: Random J Developer <random@developer.example.org>
> >
> > using a known identity (sorry, no anonymous contributions.)
>
> Quoting the kernel documentation, biemster is known contributor to us (hanging
> in sdm845-next chat room, I'm personally aware of his presence for more than ~ 2
> years).
>
> I could switch Author / Co-developed-by with me in this case, but since biemster
> did the initial work, it feels right to keep the credit.
Hanging in chat room is not a definition of a known contributor.
Absolutely anyone can be behind a nickname on IRC channel. Or Github repo.
The kernel docs is not asking for known contributors. We ask for *known
identity*.
Quoting:
"sorry, no anonymous contributions."
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-24 9:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 23:20 [PATCH v2 0/2] NFC support for two Qualcomm SDM845 phones David Heidelberg
2026-03-23 23:20 ` David Heidelberg via B4 Relay
2026-03-23 23:20 ` [PATCH v2 1/2] arm64: dts: qcom: sdm845-oneplus: Enable NFC David Heidelberg
2026-03-23 23:20 ` David Heidelberg via B4 Relay
2026-03-24 7:03 ` Krzysztof Kozlowski
2026-03-24 9:35 ` David Heidelberg
2026-03-24 9:38 ` Krzysztof Kozlowski [this message]
2026-03-23 23:20 ` [PATCH v2 2/2] arm64: dts: qcom: sdm845-shift-axolotl: " David Heidelberg
2026-03-23 23:20 ` David Heidelberg via B4 Relay
2026-03-24 13:12 ` Konrad Dybcio
2026-03-24 18:08 ` David Heidelberg
2026-03-25 11:20 ` Konrad Dybcio
2026-03-25 11:31 ` Krzysztof Kozlowski
2026-03-25 11:39 ` Konrad Dybcio
2026-03-25 20:17 ` David Heidelberg
2026-03-26 11:39 ` Konrad Dybcio
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=f69eabea-f065-437d-ba09-614ead9228ec@kernel.org \
--to=krzk@kernel.org \
--cc=amartinz@shift.eco \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=l.j.beemster@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
--cc=petr.hodina@protonmail.com \
--cc=phone-devel@vger.kernel.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 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.