08 Oct, 2009

1 commit


06 Oct, 2009

10 commits


05 Oct, 2009

23 commits

  • Previous patch d63678d607d0e37ec7abe5ceb545d7e8aab956a4 clear
    it for noMMU kernel. This one do it for MMU.

    Correct noMMU version

    Signed-off-by: Michal Simek

    Michal Simek
     
  • Signed-off-by: Michal Simek

    Michal Simek
     
  • Signed-off-by: Stephen Rothwell
    Signed-off-by: David S. Miller

    Stephen Rothwell
     
  • This reverts commit 6029336426a2b43e4bc6f4a84be8789a047d139e.

    Based upon a report by David Fries, wherein his system hangs
    on bootup with sis5513 controller, right after the CDROM
    is registered by ide-cd.c and the TOC is first read.

    Signed-off-by: David S. Miller

    David S. Miller
     
  • I'm skipping -rc2 because the -rc1 Makefile mistakenly said -rc2, so in
    order to avoid confusion, I'm jumping from -rc1 to -rc3. That way, when
    'uname' (or an oops report) says 2.6.32-rc2, there's no confusion about
    whether people perhaps meant -rc1 or -rc2.

    Linus Torvalds
     
  • Signed-off-by: Alexey Dobriyan
    Signed-off-by: Linus Torvalds

    Alexey Dobriyan
     
  • * 'acpi-pad' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6:
    acpi_pad: build only on X86
    ACPI: create Processor Aggregator Device driver

    Fixup trivial conflicts in MAINTAINERS file.

    Linus Torvalds
     
  • * 'sfi-release' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-sfi-2.6:
    SFI: remove __init from sfi_verify_table
    SFI: fix section mismatch warnings in sfi_core.c

    Linus Torvalds
     
  • * 'release' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6:
    ACPI: EC: Don't parse DSDT for EC early init on Compal
    ACPI: EC: Rewrite DMI checks
    ACPI: dock: fix "sibiling" typo
    ACPI: kill overly verbose "throttling states" log messages
    ACPI: Fix bound checks for copy_from_user in the acpi /proc code
    ACPI: fix bus scanning memory leaks
    ACPI: EC: Restart command even if no interrupts from EC
    sony-laptop: Don't unregister the SPIC driver if it wasn't registered
    sony-laptop: remove _INI call at init time
    sony-laptop: SPIC unset IRQF_SHARED, set IRQF_DISABLED
    sony-laptop: remove device_ctrl and the SPIC mini drivers

    Linus Torvalds
     
  • * 'i2c-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/jdelvare/staging:
    macintosh: Don't assume i2c device probing always succeeds
    i2c: Hide probe errors caused by ACPI resource conflicts
    i2c: Minor documentation update
    mfd: AB3100 drop unused module parameters
    Staging: IIO: tsl2561: Drop unused module parameters
    leds: leds-pca9532 - Drop unused module parameters
    ltc4215/ltc4245: Discard obsolete detect methods
    ds2482: Discard obsolete detect method
    max6875: Discard obsolete detect method
    i2c: Move misc devices documentation

    Linus Torvalds
     
  • 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: Jean Delvare
    Tested-by: Tim Shepard
    Cc: Colin Leroy

    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=14293

    Signed-off-by: Jean Delvare

    Jean Delvare
     
  • The sysfs path to i2c adapters has changed recently, update the
    documentation to reflect that change.

    Signed-off-by: Jean Delvare

    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: Jean Delvare
    Acked-by: Linus Walleij
    Cc: Samuel Ortiz

    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: Jean Delvare
    Cc: Jonathan Cameron

    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: Jean Delvare
    Cc: Richard Purdie
    Cc: Riku Voipio

    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: Jean Delvare
    Cc: Ira W. Snyder

    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: Jean Delvare
    Acked-by: Ben Gardner

    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: Jean Delvare
    Acked-by: Wolfram Sang
    Acked-by: Ben Gardner

    Jean Delvare
     
  • Some times ago the eeprom and max6875 drivers moved to
    drivers/misc/eeprom, but their documentation did not follow. It's
    finally time to get rid of Documentation/i2c/chips.

    Signed-off-by: Jean Delvare
    Cc: Ben Gardner
    Acked-by: Wolfram Sang

    Jean Delvare
     
  • * 'for-linus' of git://git.kernel.dk/linux-2.6-block: (41 commits)
    Revert "Seperate read and write statistics of in_flight requests"
    cfq-iosched: don't delay async queue if it hasn't dispatched at all
    block: Topology ioctls
    cfq-iosched: use assigned slice sync value, not default
    cfq-iosched: rename 'desktop' sysfs entry to 'low_latency'
    cfq-iosched: implement slower async initiate and queue ramp up
    cfq-iosched: delay async IO dispatch, if sync IO was just done
    cfq-iosched: add a knob for desktop interactiveness
    Add a tracepoint for block request remapping
    block: allow large discard requests
    block: use normal I/O path for discard requests
    swapfile: avoid NULL pointer dereference in swapon when s_bdev is NULL
    fs/bio.c: move EXPORT* macros to line after function
    Add missing blk_trace_remove_sysfs to be in pair with blk_trace_init_sysfs
    cciss: fix build when !PROC_FS
    block: Do not clamp max_hw_sectors for stacking devices
    block: Set max_sectors correctly for stacking devices
    cciss: cciss_host_attr_groups should be const
    cciss: Dynamically allocate the drive_info_struct for each logical drive.
    cciss: Add usage_count attribute to each logical drive in /sys
    ...

    Linus Torvalds
     
  • This reverts commit a9327cac440be4d8333bba975cbbf76045096275.

    Corrado Zoccolo 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:
    [a9327cac440be4d8333bba975cbbf76045096275] 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: Jens Axboe

    Jens Axboe
     
  • We cannot delay for the first dispatch of the async queue if it
    hasn't dispatched at all, since that could present a local user
    DoS attack vector using an app that just did slow timed sync reads
    while filling memory.

    Signed-off-by: Jens Axboe

    Jens Axboe
     

04 Oct, 2009

6 commits