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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- pci_[g|s]et_drvdata() versus ->driver_data
  - From: David KOENIG <[email protected]>

Prev by Date: Re: pci_fixup_video change blows up on sparc64
Next by Date: Re: [PATCH 7/7] Char: isicom, check kmalloc retval
Previous by thread: pci_[g|s]et_drvdata() versus ->driver_data
Next by thread: [PATCH] Replaced tty->driver_data lines with pci_get_drvdata(tty);
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]