Re: [PATCH 1/1] selftests: fpga: dfl: A test for afu interrupt support

On 6/9/20 8:45 AM, Tom Rix wrote: Why not use the ksft_* functions and frameworks to properly print out the test status and results so that tools can correctly parse it? It's generally bad-form to make up your own format. I used the the drivers/dma-buf test a basis example.  Can you point

Re: [PATCH 1/1] selftests: fpga: dfl: A test for afu interrupt support

> Why not use the ksft_* functions and frameworks to properly print out > the test status and results so that tools can correctly parse it? > > It's generally bad-form to make up your own format. I used the the drivers/dma-buf test a basis example.  Can you point me at a better example ? T >

Re: [PATCH 1/1] selftests: fpga: dfl: A test for afu interrupt support

On Tue, Jun 09, 2020 at 06:02:08AM -0700, t...@redhat.com wrote: > From: Tom Rix > > Check that the ioctl DFL_FPGA_PORT_ERR_GET_IRQ_NUM returns > an expected result. > > Tested on vf device 0xbcc1 > > Sample run with > $ sudo make -C tools/testing/selftests TARGETS=drivers/fpga run_tests > ...

[PATCH 1/1] selftests: fpga: dfl: A test for afu interrupt support

From: Tom Rix Check that the ioctl DFL_FPGA_PORT_ERR_GET_IRQ_NUM returns an expected result. Tested on vf device 0xbcc1 Sample run with $ sudo make -C tools/testing/selftests TARGETS=drivers/fpga run_tests ... ok 1 selftests: drivers/fpga: afu_intr Signed-off-by: Tom Rix ---