1. 13 12月, 2006 1 次提交
  2. 29 9月, 2006 9 次提交
  3. 27 9月, 2006 1 次提交
  4. 24 3月, 2006 2 次提交
  5. 14 2月, 2006 1 次提交
  6. 07 2月, 2006 1 次提交
    • J
      [PATCH] hwmon: Fix reboot on it87 driver load · c5e3fbf2
      Jean Delvare 提交于
      Only scan I2C address 0x2d. This is the default address and no IT87xxF
      chip was ever seen on I2C at a different address. These chips are
      better accessed through their ISA interface anyway.
      
      This fixes bug #5889, although it doesn't address the whole class
      of problems. We'd need the ability to blacklist arbitrary I2C addresses
      on systems known to contain I2C devices which behave badly when probed.
      
      Plan the I2C interface for removal as well. If nobody complains within
      a year, it will confirm my impression that the I2C interface isn't
      actually needed by anyone.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      c5e3fbf2
  7. 06 1月, 2006 4 次提交
  8. 24 11月, 2005 1 次提交
  9. 29 10月, 2005 3 次提交
  10. 06 9月, 2005 9 次提交
  11. 12 7月, 2005 1 次提交
  12. 22 6月, 2005 5 次提交
  13. 21 6月, 2005 1 次提交
  14. 19 4月, 2005 1 次提交
    • J
      [PATCH] I2C: Fix incorrect sysfs file permissions in it87 and via686a drivers · 1d66c64c
      Jean Delvare 提交于
      The it87 and via686a hardware monitoring drivers each create a sysfs
      file named "alarms" in R/W mode, while they should really create it in
      read-only mode. Since we don't provide a store function for these files,
      write attempts to these files will do something undefined (I guess) and
      bad (I am sure). My own try resulted in a locked terminal (where I
      attempted the write) and a 100% CPU load until next reboot.
      
      As a side note, wouldn't it make sense to check, when creating sysfs
      files, that readable files have a non-NULL show method, and writable
      files have a non-NULL store method? I know drivers are not supposed to
      do stupid things, but there is already a BUG_ON for several conditions
      in sysfs_create_file, so maybe we could add two more?
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      1d66c64c