linux-kernel - [PATCH 01/30] staging: comedi: add pci_dev pointer to comedi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <201207111449.15203.hartleys@visionengravers.com>
Date:	Wed, 11 Jul 2012 14:49:14 -0700
From:	H Hartley Sweeten <hartleys@...ionengravers.com>
To:	Linux Kernel <linux-kernel@...r.kernel.org>
CC:	<devel@...verdev.osuosl.org>, <abbotti@....co.uk>,
	<gregkh@...uxfoundation.org>
Subject: [PATCH 01/30] staging: comedi: add pci_dev pointer to comedi_device

The pci_dev pointer in the private driver data is used by every
comedi pci driver. Some of them only have the need for the
private data because of this pointer.

Introduce the pci_dev pointer in the comedi_device struct so it
can be used instead of needing it in the private data.

Signed-off-by: H Hartley Sweeten <hsweeten@...ionengravers.com>
Cc: Ian Abbott <abbotti@....co.uk>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
---
 drivers/staging/comedi/comedidev.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/staging/comedi/comedidev.h b/drivers/staging/comedi/comedidev.h
index de8c99c..55f2373 100644
--- a/drivers/staging/comedi/comedidev.h
+++ b/drivers/staging/comedi/comedidev.h
@@ -212,6 +212,8 @@ struct comedi_device {
 	 * DMA_NONE */
 	struct device *hw_dev;
 
+	struct pci_dev *pcidev;
+
 	const char *board_name;
 	const void *board_ptr;
 	int attached;
-- 
1.7.11

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