All of lore.kernel.org
 help / color / mirror / Atom feed
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, oe-linux-nfc@lists.linux.dev
Subject: Re: Path forward for NFC in the kernel
Date: Wed, 22 Apr 2026 20:03:35 -0700	[thread overview]
Message-ID: <20260422200335.1d0428fc@kernel.org> (raw)
In-Reply-To: <938496c6-84c1-4d53-bb56-73bbd7b2bdd7@ixit.cz>

On Wed, 22 Apr 2026 15:11:16 +0200 David Heidelberg wrote:
> 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.

Sounds good. The discussion taking long is perfectly fine. Main concern
to us is not hearing any response for a long time. Then we have to guess
whether the maintainer is planning to respond, or AWOL.

> 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.

Works! :)

  reply	other threads:[~2026-04-23  3:03 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
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 [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=20260422200335.1d0428fc@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=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 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.