linux-kernel - Re: pci_[g|s]et_drvdata() versus ->driver

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-prev] [day] [month] [year] [list]

Date:	Thu, 19 Oct 2006 23:20:14 +0100
From:	Russell King <rmk+lkml@....linux.org.uk>
To:	David KOENIG <karhudever@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: pci_[g|s]et_drvdata() versus ->driver_data

On Thu, Oct 19, 2006 at 11:32:44AM -0700, David KOENIG wrote:
> Is there any reason for some drivers that I should leave references as
> foo->driver_data instead of pci_get_drvdata(foo)?

When "foo" is not a struct pci_dev ?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core
-
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/