linux-nfc.lists.01.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.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 16:21:25 -0400	[thread overview]
Message-ID: <cd7a0110-702a-6e14-527e-fb4b53705870@canonical.com> (raw)
In-Reply-To: 20210512170135.GB222094@animalcreek.com

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

On 12/05/2021 13:01, Mark Greer wrote:
> On Wed, May 12, 2021@05:32:35PM +0200, Frieder Schrempf wrote:
>> On 12.05.21 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.
>>
>> That's great, thanks!
>>
>> Maybe you also want to have a look@the userspace side and talk to Mark Greer (on cc). He recently said, that he is supposed to be taking over maintenance for the neard daemon (see this thread: [1]) which currently looks like it's close to being dead (no release for several years, etc.).
>>
>> I don't know much about the NFC stack and if/how people use it, but without reliable and maintained userspace tooling, the whole thing seems of little use in the long run. Qt has already dropped their neard support for Qt 6 [2], which basically means the mainline NFC stack won't be supported anymore in one of the most common application frameworks for IoT/embedded.
>>
>> [1] https://lists.01.org/hyperkitty/list/linux-nfc@lists.01.org/thread/OHD5IQHYPFUPUFYWDMNSVCBNO24M45VK/
>> [2] https://bugreports.qt.io/browse/QTBUG-81824
> 
> Re: QT - I've already talked to Alex Blasche from QT (CC'd).  With some
> work we can get Linux NFC/neard back into their good graces.  I/we need
> to find time to put in the work, though.
> 
> An example of the issues they have seen is:
> 
> 	https://bugreports.qt.io/browse/QTBUG-43802
> 
> Another issue I have--and I suspect you, Krzysztof, have as well--is
> lack of hardware.  If anyone reading this wants to volunteer to be a
> tester, please speak up.

Yes, testing would be very appreciated. I don't know how many unit tests
neard has, but maybe some mockups with unit testing would solve some of
problems?



Best regards,
Krzysztof

             reply	other threads:[~2021-05-12 20:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 20:21 Krzysztof Kozlowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-13  1:35 [linux-nfc] Re: [PATCH 1/2] MAINTAINERS: nfc: add Krzysztof Kozlowski as maintainer Mark Greer
2021-05-12 21:31 Krzysztof Kozlowski
2021-05-12 20:22 Krzysztof Kozlowski
2021-05-12 17:01 Mark Greer
2021-05-12 15:32 Frieder Schrempf
2021-05-12 15:15 Mark Greer
2021-05-12 14:43 [linux-nfc] " 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
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

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=cd7a0110-702a-6e14-527e-fb4b53705870@canonical.com \
    --to=krzysztof.kozlowski@canonical.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).