[PATCH 6/9] Staging: comedi: fix line over 80 character issue in cb_pcidio.c

From: Ravishankar Karkala Mallikarjunayya
Date: Fri Sep 30 2011 - 09:19:36 EST


This is a patch to the cb_pcidio.c file that fixes up a line over 80 character warning found by the checkpatch.pl tool

Signed-off-by: Ravishankar Karkala Mallikarjunayya <ravishankar.km@xxxxxxxxxxxxxxx>
---
drivers/staging/comedi/drivers/cb_pcidio.c | 15 ++++++++++-----
1 files changed, 10 insertions(+), 5 deletions(-)

diff --git a/drivers/staging/comedi/drivers/cb_pcidio.c b/drivers/staging/comedi/drivers/cb_pcidio.c
index 85cc78d..40a3eb0 100644
--- a/drivers/staging/comedi/drivers/cb_pcidio.c
+++ b/drivers/staging/comedi/drivers/cb_pcidio.c
@@ -104,9 +104,12 @@ MODULE_DEVICE_TABLE(pci, pcidio_pci_table);
*/
#define thisboard ((const struct pcidio_board *)dev->board_ptr)

-/* this structure is for data unique to this hardware driver. If
- several hardware drivers keep similar information in this structure,
- feel free to suggest moving the variable to the struct comedi_device struct. */
+/*
+ * this structure is for data unique to this hardware driver. If
+ * several hardware drivers keep similar information in this structure,
+ * feel free to suggest moving the variable to the struct comedi_device
+ * struct.
+ */
struct pcidio_private {
int data; /* currently unused */

@@ -114,9 +117,11 @@ struct pcidio_private {
struct pci_dev *pci_dev;

/* used for DO readback, currently unused */
- unsigned int do_readback[4]; /* up to 4 unsigned int suffice to hold 96 bits for PCI-DIO96 */
+ /* up to 4 unsigned int suffice to hold 96 bits for PCI-DIO96 */
+ unsigned int do_readback[4];

- unsigned long dio_reg_base; /* address of port A of the first 8255 chip on board */
+ /* address of port A of the first 8255 chip on board */
+ unsigned long dio_reg_base;
};

/*
--
1.7.6.2

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/