From: David Heidelberg <david@ixit.cz>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Michael Thalmeier <michael.thalmeier@hale.at>,
Raymond Hackley <raymondhackley@protonmail.com>,
Michael Walle <michael@walle.cc>,
Bongsu Jeon <bongsu.jeon@samsung.com>,
Mark Greer <mgreer@animalcreek.com>
Cc: netdev@vger.kernel.org, oe-linux-nfc@lists.linux.dev
Subject: Re: Path forward for NFC in the kernel
Date: Fri, 17 Apr 2026 15:32:48 +0200 [thread overview]
Message-ID: <316ae06b-ed7f-4fa6-9b91-fa45f088dc43@ixit.cz> (raw)
In-Reply-To: <9c4a4acf-b4f1-4e84-93bf-cdf080cb9970@kernel.org>
On 17/04/2026 09:18, Krzysztof Kozlowski wrote:
> On 16/04/2026 19:10, Jakub Kicinski wrote:
>> Hi folks!
>>
>> We are struggling to keep up with the number of security reports and AI
>> generated patches in the kernel. NFC is infamous for being a huge CVE
>> magnet. We need someone to step up as a maintainer, create an NFC tree
>> and handle all the incoming submissions. Send us (or Linus if you
>> prefer) periodic PRs, like WiFi, Bluetooth etc. do. If that does not
>> happen I'm afraid we'll have to move the NFC code out of the tree,
>> put it up on GH or some such, and let it accumulate CVEs there..
>>
>> I'm planning to send a PR to Linus to shed the unmaintained code early
>> next week. We need to have a maintainer established by then.
>
> +Cc David Heidelberg recently trying to use Linux NFC stack,
>
+Cc oe-linux-nfc@lists.linux.dev
For now we had NFC related discussion in our sdm845-next channel, but I brought
Matrix channel [1] for the kernel, neard, user-space discussion, so people can
share and interact in real-time (the chat content is public without needing to
join the room).
David
[1] https://matrix.to/#/#linux-nfc:ixit.cz
...
prev parent reply other threads:[~2026-04-17 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 17:10 Path forward for NFC in the kernel Jakub Kicinski
2026-04-17 6:35 ` Michael Walle
2026-04-17 7:18 ` Krzysztof Kozlowski
2026-04-17 8:12 ` David Heidelberg
2026-04-17 8:54 ` Michael Walle
2026-04-17 12:16 ` David Heidelberg
2026-04-17 13:32 ` David Heidelberg [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=316ae06b-ed7f-4fa6-9b91-fa45f088dc43@ixit.cz \
--to=david@ixit.cz \
--cc=bongsu.jeon@samsung.com \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=mgreer@animalcreek.com \
--cc=michael.thalmeier@hale.at \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
--cc=raymondhackley@protonmail.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