From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Mark Greer <mgreer@animalcreek.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] nfc: MAINTAINERS: Orphan the NFC and look for new maintainers
Date: Fri, 16 Jan 2026 19:14:58 +0100 [thread overview]
Message-ID: <f824d9a0-2f34-4c5d-acd6-e59a85111be2@oss.qualcomm.com> (raw)
In-Reply-To: <bddcea45-388e-4a97-a404-c193e915eb77@animalcreek.com>
On 15/01/2026 16:36, Mark Greer wrote:
> On 1/9/26 3:11 AM, Krzysztof Kozlowski wrote:
>> NFC stack in Linux is in poor shape, with several bugs being discovered
>> last years via fuzzing, not much new development happening and limited
>> review and testing. It requires some more effort than drive-by reviews
>> I have been offering last one or two years.
>>
>> I don't have much time nor business interests to keep looking at NFC,
>> so let's drop me from maintainers to clearly indicate that more hands
>> are needed.
>>
>> Cc: Mark Greer <mgreer@animalcreek.com>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
>
> Acked-by: Mark Greer <mgreer@animalcreek.com>
>
>> ---
>>
>> One might argue that poor/non-responsive maintainer is better than no
>> maintainer, but I think better to admit that real state of affairs, so
>> people would see there is vacancy to take.
>> ---
>
> Thank you so much for the work you've done on this Krzysztof. I was
> supposed to help you with some of this but I didn't. I'm pretty busy
> too so I'm not sure when this situation will improve for me or in
> general. Maybe someone will step up.
No worries. If you ever want to come back to taking care about NFC, the
position waits. :)
Best regards,
Krzysztof
prev parent reply other threads:[~2026-01-16 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 10:11 Krzysztof Kozlowski
2026-01-15 15:36 ` Mark Greer
2026-01-16 18:14 ` 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=f824d9a0-2f34-4c5d-acd6-e59a85111be2@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgreer@animalcreek.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
all inboxes | Powered by JetHome®