public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Jakub Kicinski <kuba@kernel.org>
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, oe-linux-nfc@lists.linux.dev
Subject: Re: Path forward for NFC in the kernel
Date: Wed, 22 Apr 2026 15:11:16 +0200	[thread overview]
Message-ID: <938496c6-84c1-4d53-bb56-73bbd7b2bdd7@ixit.cz> (raw)
In-Reply-To: <20260421071044.67a3cee1@kernel.org>

On 21/04/2026 16:10, Jakub Kicinski wrote:
> 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? :)

Hi,

thanks for giving me the opportunity - I appreciate the trust, especially given 
the circumstances.

Yes, this is broadly in line with what I had in mind. To clarify the “limited 
reviews and basic maintenance” phrasing: that was more an attempt to set 
expectations conservatively. I’m prepared to take on the responsibilities you 
outlined — maintaining a tree, collecting and triaging patches, and sending 
regular pull requests.

Regarding reviews and responsiveness: I can do the 48h turnaround for initial 
feedback on submissions (excluding weekends, and occasional travel), and I’ll 
make sure no patch sits unattended. For more complex changes where my current 
NFC-specific knowledge may be a limiting factor, I’ll seek input rather than let 
things stall.

I’m also planning to ramp up my familiarity with the NFC stack as I go, so I 
expect both the quality and depth of my reviews to improve over time.

If that works for you, I’ll proceed with setting up a public tree and start 
tracking incoming patches.

Thanks again for the support - I’ll likely take you up on that, especially early on.

Best regards,
David

  reply	other threads:[~2026-04-22 13:11 UTC|newest]

Thread overview: 10+ 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
2026-04-22 13:11       ` David Heidelberg [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=938496c6-84c1-4d53-bb56-73bbd7b2bdd7@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