As indicated by checkpatch.pl, "WARNING: Use of volatile is usually
wrong: ...", the 'count' member of the private data does not need to
be volatile.

Signed-off-by: H Hartley Sweeten <hswee...@visionengravers.com>
Cc: Ian Abbott <abbo...@mev.co.uk>
Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org>
---
 drivers/staging/comedi/drivers/ni_at_a2150.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/staging/comedi/drivers/ni_at_a2150.c 
b/drivers/staging/comedi/drivers/ni_at_a2150.c
index 69e543a..8265322 100644
--- a/drivers/staging/comedi/drivers/ni_at_a2150.c
+++ b/drivers/staging/comedi/drivers/ni_at_a2150.c
@@ -146,8 +146,7 @@ static const struct a2150_board a2150_boards[] = {
 };
 
 struct a2150_private {
-
-       volatile unsigned int count;    /* number of data points left to be 
taken */
+       unsigned int count;     /* number of data points left to be taken */
        unsigned int dma;       /*  dma channel */
        uint16_t *dma_buffer;   /*  dma buffer */
        unsigned int dma_transfer_size; /*  size in bytes of dma transfers */
-- 
2.0.3

_______________________________________________
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Reply via email to