linux-nfc.lists.01.org archive mirror
 help / color / mirror / Atom feed
From: Mark Greer <mgreer@animalcreek.com>
To: linux-nfc@lists.01.org
Subject: [linux-nfc] Re: [PATCH 1/2] MAINTAINERS: nfc: add Krzysztof Kozlowski as maintainer
Date: Wed, 12 May 2021 09:49:52 -0700	[thread overview]
Message-ID: <20210512164952.GA222094@animalcreek.com> (raw)
In-Reply-To: d498c949-3b1e-edaa-81ed-60573cfb6ee9@canonical.com

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

On Wed, May 12, 2021@11:43:13AM -0400, Krzysztof Kozlowski wrote:
> On 12/05/2021 11:11, Daniel Lezcano wrote:
> > On 12/05/2021 16:43, Krzysztof Kozlowski wrote:
> >> The NFC subsystem is orphaned.  I am happy to spend some cycles to
> >> review the patches, send pull requests and in general keep the NFC
> >> subsystem running.
> >>
> >> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> >>
> >> ---
> >>
> >> I admit I don't have big experience in NFC part but this will be nice
> >> opportunity to learn something new. 
> > 
> > NFC has been lost in the limbos since a while. Good to see someone
> > volunteering to take care of it.
> > 
> > May I suggest to create a simple nfc reading program in the 'tools'
> > directory (could be a training exercise ;)
> > 
> 
> Noted, thanks. I also need to get a simple hardware dongle for this....

Krzysztof, the NFC portion of the kernel has a counterpart in userspace
called neard.  I'm supposed to be maintaining it but I have next to no
time to do so.  If you have spare cycles, any help would be appreciated.

Anyway, in neard, there are some simple test scripts (python2 - I/we need
to update to python3).  The current home of neard is:

git://git.kernel.org/pub/scm/network/nfc/neard.git

Mark
--

         reply	other threads:[~2021-05-12 16:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 14:43 [linux-nfc] [PATCH 1/2] MAINTAINERS: nfc: add Krzysztof Kozlowski as maintainer Krzysztof Kozlowski
2021-05-12 15:11 ` [linux-nfc] " Daniel Lezcano
2021-05-12 15:43   ` Krzysztof Kozlowski
2021-05-12 16:49     ` Mark Greer [this message]
2021-07-09  9:24       ` Krzysztof Kozlowski
2021-07-15 18:34         ` Mark Greer
2021-07-16 10:17           ` Krzysztof Kozlowski
2021-07-16 17:15             ` Mark Greer
2021-07-16 18:17               ` Krzysztof Kozlowski
2021-07-16 19:32                 ` Mark Greer
2021-05-12 15:15 Mark Greer
2021-05-12 15:32 Frieder Schrempf
2021-05-12 17:01 Mark Greer
2021-05-12 20:21 Krzysztof Kozlowski
2021-05-12 20:22 Krzysztof Kozlowski
2021-05-12 21:31 Krzysztof Kozlowski
2021-05-13  1:35 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=20210512164952.GA222094@animalcreek.com \
    --to=mgreer@animalcreek.com \
    --cc=linux-nfc@lists.01.org \
    /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;
as well as URLs for NNTP newsgroup(s).