[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210106090112.04ebf38f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Wed, 6 Jan 2021 09:01:12 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Bongsu Jeon <bongsu.jeon2@...il.com>
Cc: davem@...emloft.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-nfc@...ts.01.org,
Bongsu Jeon <bongsu.jeon@...sung.com>
Subject: Re: [PATCH net-next] nfc: Add a virtual nci device driver
On Wed, 6 Jan 2021 08:16:47 +0900 Bongsu Jeon wrote:
> On Tue, Jan 5, 2021 at 4:48 AM Jakub Kicinski <kuba@...nel.org> wrote:
> > > thank you for your answer.
> > > I think that neard(NFC deamon) is necessary to test the NCI subsystem
> > > meaningfully.
> > > The NCI virtual device in user space can communicate with neard
> > > through this driver.
> > > Is it enough to make NCI virtual device at tools/nfc for some test?
> >
> > I'm not sure if I understand. Are you asking if it's okay for the test
> > or have a dependency on neard?
>
> Sorry for confusing you.
> There is no dependency between neard and a NCI virtual device.
> But, To test the NCI module, it is necessary to make an application like neard.
> Is it okay to just make a NCI virtual device as a tool at tools/nfc
> without the application?
Meaning the device will be created but there will be no test cases in
the tree?
What we'd like to see is some form of a test which would exercise the
NFC-related kernel code on such a device and can signal success /
failure. It doesn't have to be very complex.
You can build a more complex user space applications and tests
separately.
Powered by blists - more mailing lists