1. 05 10月, 2009 9 次提交
    • J
      macintosh: Don't assume i2c device probing always succeeds · 6f6b35e1
      Jean Delvare 提交于
      If i2c device probing fails, then there is no driver to dereference
      after calling i2c_new_device(). Stop assuming that probing will always
      succeed, to avoid NULL pointer dereferences. We have an easier access
      to the driver anyway.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Tested-by: NTim Shepard <shep@alum.mit.edu>
      Cc: Colin Leroy <colin@colino.net>
      6f6b35e1
    • J
      i2c: Hide probe errors caused by ACPI resource conflicts · 18669eab
      Jean Delvare 提交于
      When an ACPI resource conflict is detected, error messages are already
      printed by ACPI. There's no point in causing the driver core to print
      more error messages, so return one of the error codes for which no
      message is printed.
      
      This fixes bug #14293:
      http://bugzilla.kernel.org/show_bug.cgi?id=14293Signed-off-by: NJean Delvare <khali@linux-fr.org>
      18669eab
    • J
      mfd: AB3100 drop unused module parameters · dcffa125
      Jean Delvare 提交于
      The I2C_CLIENT_INSMOD_1 macro is only useful for i2c drivers which
      implement device detection. The ab3100 driver doesn't, so there is no
      point in calling it.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Acked-by: NLinus Walleij <linus.walleij@stericsson.com>
      Cc: Samuel Ortiz <sameo@linux.intel.com>
      dcffa125
    • J
      Staging: IIO: tsl2561: Drop unused module parameters · 0d83f18b
      Jean Delvare 提交于
      The I2C_CLIENT_INSMOD macro is only useful for i2c drivers which
      implement device detection. The tsl2561 driver doesn't, so there
      is no point in calling it.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Cc: Jonathan Cameron <jic23@cam.ac.uk>
      0d83f18b
    • J
      leds: leds-pca9532 - Drop unused module parameters · 77279862
      Jean Delvare 提交于
      The I2C_CLIENT_INSMOD_1 macro is only useful for i2c drivers which
      implement device detection. The leds-pca9532 driver doesn't, so there
      is no point in calling it.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Cc: Richard Purdie <rpurdie@rpsys.net>
      Cc: Riku Voipio <riku.voipio@iki.fi>
      77279862
    • J
      ltc4215/ltc4245: Discard obsolete detect methods · 2d2a7cff
      Jean Delvare 提交于
      There is no point in implementing a detect callback for the LTC4215
      and LTC4245, as these devices can't be detected. It was there solely
      to handle "force" module parameters to instantiate devices, but now
      we have a better sysfs interface that can do the same.
      
      So we can get rid of the ugly module parameters and the detect
      callbacks. This shrinks the binary module sizes by 36% and 46%,
      respectively.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Cc: Ira W. Snyder <iws@ovro.caltech.edu>
      2d2a7cff
    • J
      ds2482: Discard obsolete detect method · 0314b020
      Jean Delvare 提交于
      There is no point in implementing a detect callback for the DS2482, as
      this device can't be detected. It was there solely to handle "force"
      module parameters to instantiate devices, but now we have a better sysfs
      interface that can do the same.
      
      So we can get rid of the ugly module parameters and the detect callback.
      This shrinks the binary module size by 21%.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Acked-by: NBen Gardner <gardner.ben@gmail.com>
      0314b020
    • J
      max6875: Discard obsolete detect method · b835d7fb
      Jean Delvare 提交于
      There is no point in implementing a detect callback for the MAX6875, as
      this device can't be detected. It was there solely to handle "force"
      module parameters to instantiate devices, but now we have a better sysfs
      interface that can do the same.
      
      So we can get rid of the ugly module parameters and the detect callback.
      This basically divides the binary module size by 2.
      Signed-off-by: NJean Delvare <khali@linux-fr.org>
      Acked-by: NWolfram Sang <w.sang@pengutronix.de>
      Acked-by: NBen Gardner <gardner.ben@gmail.com>
      b835d7fb
    • J
      Revert "Seperate read and write statistics of in_flight requests" · 0f78ab98
      Jens Axboe 提交于
      This reverts commit a9327cac.
      
      Corrado Zoccolo <czoccolo@gmail.com> reports:
      
      "with 2.6.32-rc1 I started getting the following strange output from
      "iostat -kx 2":
      Linux 2.6.31bisect (et2) 	04/10/2009 	_i686_	(2 CPU)
      
      avg-cpu:  %user   %nice %system %iowait  %steal   %idle
                10,70    0,00    3,16   15,75    0,00   70,38
      
      Device:         rrqm/s   wrqm/s     r/s     w/s    rkB/s    wkB/s
      avgrq-sz avgqu-sz   await  svctm  %util
      sda              18,22     0,00    0,67    0,01    14,77     0,02
      43,94     0,01   10,53 39043915,03 2629219,87
      sdb              60,89     9,68   50,79    3,04  1724,43    50,52
      65,95     0,70   13,06 488437,47 2629219,87
      
      avg-cpu:  %user   %nice %system %iowait  %steal   %idle
                 2,72    0,00    0,74    0,00    0,00   96,53
      
      Device:         rrqm/s   wrqm/s     r/s     w/s    rkB/s    wkB/s
      avgrq-sz avgqu-sz   await  svctm  %util
      sda               0,00     0,00    0,00    0,00     0,00     0,00
      0,00     0,00    0,00   0,00 100,00
      sdb               0,00     0,00    0,00    0,00     0,00     0,00
      0,00     0,00    0,00   0,00 100,00
      
      avg-cpu:  %user   %nice %system %iowait  %steal   %idle
                 6,68    0,00    0,99    0,00    0,00   92,33
      
      Device:         rrqm/s   wrqm/s     r/s     w/s    rkB/s    wkB/s
      avgrq-sz avgqu-sz   await  svctm  %util
      sda               0,00     0,00    0,00    0,00     0,00     0,00
      0,00     0,00    0,00   0,00 100,00
      sdb               0,00     0,00    0,00    0,00     0,00     0,00
      0,00     0,00    0,00   0,00 100,00
      
      avg-cpu:  %user   %nice %system %iowait  %steal   %idle
                 4,40    0,00    0,73    1,47    0,00   93,40
      
      Device:         rrqm/s   wrqm/s     r/s     w/s    rkB/s    wkB/s
      avgrq-sz avgqu-sz   await  svctm  %util
      sda               0,00     0,00    0,00    0,00     0,00     0,00
      0,00     0,00    0,00   0,00 100,00
      sdb               0,00     4,00    0,00    3,00     0,00    28,00
      18,67     0,06   19,50 333,33 100,00
      
      Global values for service time and utilization are garbage. For
      interval values, utilization is always 100%, and service time is
      higher than normal.
      
      I bisected it down to:
      [a9327cac] Seperate read and write
      statistics of in_flight requests
      and verified that reverting just that commit indeed solves the issue
      on 2.6.32-rc1."
      
      So until this is debugged, revert the bad commit.
      Signed-off-by: NJens Axboe <jens.axboe@oracle.com>
      0f78ab98
  2. 04 10月, 2009 1 次提交
    • L
      tty: Avoid dropping ldisc_mutex over hangup tty re-initialization · 0b5759c6
      Linus Torvalds 提交于
      A couple of people have hit the WARN_ON() in drivers/char/tty_io.c,
      tty_open() that is unhappy about seeing the tty line discipline go away
      during the tty hangup. See for example
      
      	http://bugzilla.kernel.org/show_bug.cgi?id=14255
      
      and the reason is that we do the tty_ldisc_halt() outside the
      ldisc_mutex in order to be able to flush the scheduled work without a
      deadlock with vhangup_work.
      
      However, it turns out that we can solve this particular case by
      
       - using "cancel_delayed_work_sync()" in tty_ldisc_halt(), which waits
         for just the particular work, rather than synchronizing with any
         random outstanding pending work.
      
         This won't deadlock, since the buf.work we synchronize with doesn't
         care about the ldisc_mutex, it just flushes the tty ldisc buffers.
      
       - realize that for this particular case, we don't need to wait for any
         hangup work, because we are inside the hangup codepaths ourselves.
      
      so as a result we can just drop the flush_scheduled_work() entirely, and
      then move the tty_ldisc_halt() call to inside the mutex.  That way we
      never expose the partially torn down ldisc state to tty_open(), and hold
      the ldisc_mutex over the whole sequence.
      Reported-by: NIngo Molnar <mingo@elte.hu>
      Reported-by: NHeinz Diehl <htd@fancy-poultry.org>
      Cc: stable@kernel.org
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      0b5759c6
  3. 03 10月, 2009 16 次提交
  4. 02 10月, 2009 14 次提交