Thread (7 messages) 7 messages, 2 authors, 2021-01-07

Re: [PATCH net-next] nfc: Add a virtual nci device driver

From: Jakub Kicinski <kuba@kernel.org>
Date: 2021-01-06 17:02:02
Also in: lkml

On Wed, 6 Jan 2021 08:16:47 +0900 Bongsu Jeon wrote:
On Tue, Jan 5, 2021 at 4:48 AM Jakub Kicinski [off-list ref] wrote:
quoted
quoted
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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help