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 18:35:38 -0700 [thread overview]
Message-ID: <20210513013538.GA239989@animalcreek.com> (raw)
In-Reply-To: cd7a0110-702a-6e14-527e-fb4b53705870@canonical.com
[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]
On Wed, May 12, 2021@04:21:25PM -0400, Krzysztof Kozlowski wrote:
> On 12/05/2021 13:01, Mark Greer wrote:
> > 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?
I'm not sure what you mean by this. Do you mean creating some tests that
sit directly on top of the kernel and test the kernel parts (e.g., use
netlink)? If so, that would be useful but you may end up implementing
some of the NFC stack. If you mean more/better tests that use neard to
exercise the whole stack then that would be really good too.
Speaking of NFC stack, the NFC forum has their specs paywalled which is
a real bummer/pain. I can try reaching out to them to see if they will
help us help their mission but I'm not hopeful.
FYI, most of the issues that I ran into and know still exist are
timing/race issues in neard. I'm sure if we tested more, we could find
some in the kernel though.
Mark
--
next reply other threads:[~2021-05-13 1:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 1:35 Mark Greer [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-12 21:31 [linux-nfc] Re: [PATCH 1/2] MAINTAINERS: nfc: add Krzysztof Kozlowski as maintainer Krzysztof Kozlowski
2021-05-12 20:22 Krzysztof Kozlowski
2021-05-12 20:21 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=20210513013538.GA239989@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 read-only IMAP folder(s) and NNTP newsgroup(s).