1. 12 9月, 2005 2 次提交
    • C
      [ALSA] sparse address space annotations · 4d23359b
      Clemens Ladisch 提交于
      ALSA Core,RawMidi Midlevel,ALSA<-OSS emulation,ALSA sequencer
      RME32 driver,RME96 driver,EMU10K1/EMU10K2 driver,NM256 driver
      Add sparse annotations where we do strange this with __iomem/__user
      pointers.
      Signed-off-by: NClemens Ladisch <clemens@ladisch.de>
      4d23359b
    • J
      [ALSA] snd-ca0106, snd-emu10k1: Add symlink in the sys tree. · 025cd2f6
      James Courtier-Dutton 提交于
      CA0106 driver,EMU10K1/EMU10K2 driver
      A thread appeared on the LKML. This patch implements the fix.
      
      Question:
      in sysfs, /sys/bus/*/drivers lists the driver names, with their exported .name (eg. '.name = 'EMU10K1_Audigy'' in the module code, from now on 'driver name'). In /sys/modules, the kernel modules are listed with their module name, eg. snd_emu10k1. However, it seems to me that in sysfs, there is no way in particular to tell, which module has which .name. That is, that snd_emu10k1 is EMU10K1_Audigy and vice versa.
      
      I wonder whether it wouldn't be possible to add a symlink to the particular module from the driver, and/or from the module to the driver, so the list of devices handled by the module and the module name would be accessible. This way, I would know which driver name corresponds to which module name and vice versa.
      
      Answer:
      For PCI drivers, just add the line:
      	.owner = THIS_MODULE,
      
      to their struct pci_driver definition and you will get the symlink
      created for you.
      Signed-off-by: NJames Courtier-Dutton <James@superbug.co.uk>
      025cd2f6
  2. 30 8月, 2005 6 次提交
  3. 28 7月, 2005 8 次提交
  4. 22 6月, 2005 2 次提交
  5. 29 5月, 2005 21 次提交
  6. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4