All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Walle" <mwalle@kernel.org>
To: "Jakub Kicinski" <kuba@kernel.org>,
	"Michael Thalmeier" <michael.thalmeier@hale.at>,
	"Raymond Hackley" <raymondhackley@protonmail.com>,
	"Bongsu Jeon" <bongsu.jeon@samsung.com>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	"Mark Greer" <mgreer@animalcreek.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: Path forward for NFC in the kernel
Date: Fri, 17 Apr 2026 08:35:41 +0200	[thread overview]
Message-ID: <DHV7ZMEI94AT.3O3RRPYOM7LPI@kernel.org> (raw)
In-Reply-To: <20260416101041.4c533306@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]

Hi,

On Thu Apr 16, 2026 at 7:10 PM CEST, 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.

Thanks for asking, but I'm busy renovating my house, sorry. I
couldn't put much work into that. The former is already stressful
enough :)

-michael

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]

  reply	other threads:[~2026-04-17  6:35 UTC|newest]

Thread overview: 11+ 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 [this message]
2026-04-17  7:18 ` Krzysztof Kozlowski
2026-04-17  8:12   ` David Heidelberg
2026-04-21 14:10     ` Jakub Kicinski
2026-04-22 13:11       ` David Heidelberg
2026-04-23  3:03         ` Jakub Kicinski
2026-04-17  8:54   ` Michael Walle
2026-04-17 12:16     ` David Heidelberg
2026-04-17 13:32   ` David Heidelberg
2026-04-20 15:31   ` Mark Greer

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=DHV7ZMEI94AT.3O3RRPYOM7LPI@kernel.org \
    --to=mwalle@kernel.org \
    --cc=bongsu.jeon@samsung.com \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=mgreer@animalcreek.com \
    --cc=michael.thalmeier@hale.at \
    --cc=netdev@vger.kernel.org \
    --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 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.