* pci_[g|s]et_drvdata() versus ->driver_data
@ 2006-10-19 18:32 David KOENIG
2006-10-19 22:20 ` Russell King
0 siblings, 1 reply; 2+ messages in thread
From: David KOENIG @ 2006-10-19 18:32 UTC (permalink / raw)
To: linux-kernel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Is there any reason for some drivers that I should leave references as
foo->driver_data instead of pci_get_drvdata(foo)?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFN8TLmhCgVPlWJY8RAv4lAJ9VrJg+DlXt+AMvVBBbMSgl/3UqzgCgpynk
cGm7n7hfEdgWZQxZ0qeXhqE=
=0KXz
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: pci_[g|s]et_drvdata() versus ->driver_data
2006-10-19 18:32 pci_[g|s]et_drvdata() versus ->driver_data David KOENIG
@ 2006-10-19 22:20 ` Russell King
0 siblings, 0 replies; 2+ messages in thread
From: Russell King @ 2006-10-19 22:20 UTC (permalink / raw)
To: David KOENIG; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-10-19 22:20 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-19 18:32 pci_[g|s]et_drvdata() versus ->driver_data David KOENIG
2006-10-19 22:20 ` Russell King
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox