From: Jakub Kicinski <kuba@kernel.org>
To: David Heidelberg <david@ixit.cz>
Cc: Krzysztof Kozlowski <krzk@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>,
netdev@vger.kernel.org
Subject: Re: Path forward for NFC in the kernel
Date: Tue, 21 Apr 2026 07:10:44 -0700 [thread overview]
Message-ID: <20260421071044.67a3cee1@kernel.org> (raw)
In-Reply-To: <1725ea8d-ac1f-49d2-8d8c-2e09721454c2@ixit.cz>
On Fri, 17 Apr 2026 10:12:22 +0200 David Heidelberg wrote:
> > +Cc David Heidelberg recently trying to use Linux NFC stack,
> >
> > Just "collecting" patches is not a big deal, I could do this, but
> > actually reviewing the patches with necessary due diligence is the
> > effort I could not provide in a reasonable time frame. And picking up
> > patches without proper review feels risky...
>
> Hello Krzystof, Jakub,
>
> thanks for putting me into loop.
>
> I can do limited reviews and basic maintenance. My knowledge about NFC is for
> now somehow limited (but I'm willing to invest my limited time into learning more).
>
> As "I & LLM" wrote [1] userspace very basic reader for GNOME and planning to do
> more tight integration into GNOME, so would make sense to keep the kernel stack
> alive.
Hi David!
Sorry for the delay, we (core maintainers) discussed the situation
off-list and since our choices are either delete all this code or give
you a chance, everyone agreed that the latter is strictly better :)
It's a little unusual to designate someone who doesn't have a proven
track record acting as a de facto maintainer, but such are the times...
Our expectation would be that:
- you'd create your own tree to gather NFC patches and send us
periodic pull requests every 2 or 3 weeks, with what you gathered
- act upon submissions within 48h of posting (excluding weekends)
Of course we'll happy to provide any support and guidance you need,
specially for the first few months.
Is this what you had in mind? The phrase "limited reviews and basic
maintenance" is slightly worrying, we assumed it's an expression of
modesty rather than commitment? :)
next prev parent reply other threads:[~2026-04-21 14:10 UTC|newest]
Thread overview: 9+ 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-21 14:10 ` Jakub Kicinski [this message]
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=20260421071044.67a3cee1@kernel.org \
--to=kuba@kernel.org \
--cc=bongsu.jeon@samsung.com \
--cc=david@ixit.cz \
--cc=krzk@kernel.org \
--cc=mgreer@animalcreek.com \
--cc=michael.thalmeier@hale.at \
--cc=michael@walle.cc \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox