23 Feb, 2011

13 commits

  • Use new truncation sequence in UDF and fix up error handling in the
    code.

    Signed-off-by: Jan Kara

    Jan Kara
     
  • * 'for-2639-rc4/i2c-fixes' of git://git.fluff.org/bjdooks/linux:
    i2c-omap: fixup commit cb527ede1bf6ff2008a025606f25344b8ed7b4ac whitespace
    i2c-omap: Double clear of ARDY status in IRQ handler
    i2c-omap: fix build for !CONFIG_SUSPEND
    i2c-omap: fix static suspend vs. runtime suspend
    i2c-stu300: make sure adapter-name is terminated

    Linus Torvalds
     
  • * 'usb-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6:
    Revert "USB: Reset USB 3.0 devices on (re)discovery"
    USB: musb: omap2430: fix kernel panic on reboot
    sierra: add new ID for Airprime/Sierra USB IP modem
    USB: serial/usb_wwan, fix tty NULL dereference
    USB: Reset USB 3.0 devices on (re)discovery
    USB: Add quirk for Samsung Android phone modem
    USB: Add Samsung SGH-I500/Android modem ID switch to visor driver
    USB: add quirks entry for Keytouch QWERTY Panel
    usb: musb: omap2430: fix kernel panic on reboot
    usb: musb: fix build breakage

    Linus Torvalds
     
  • Fixup the whitespace error noticed in cb527ede1bf6ff2008a025606f25344b8ed7b4ac

    Signed-off-by: Ben Dooks

    Ben Dooks
     
  • This errata occurs when the ARDY interrupt generation is enabled.
    At the begining of every new transaction the ARDY interrupt is cleared.

    On continuous i2c transactions where after clearing the ARDY bit from
    I2C_STAT register (clearing the interrupt), the IRQ line is reasserted and the
    I2C_STAT[ARDY] bit set again on 1. In fact, the ARDY status bit is not cleared
    at the write access to I2C_STAT[ARDY] and only the IRQ line is deasserted and
    then reasserted. This is not captured in the usual errata documents.

    The workaround is to have a double clear of ARDY status in irq handler.

    Signed-off-by: Richard woodruff
    Signed-off-by: Keerthy
    Signed-off-by: Ben Dooks

    Richard woodruff
     
  • fix the build break when !CONFIG_SUSPEND

    drivers/i2c/busses/i2c-omap.c:1173: error: lvalue required as unary '&' operand
    make[3]: *** [drivers/i2c/busses/i2c-omap.o] Error 1
    make[2]: *** [drivers/i2c/busses] Error 2
    make[1]: *** [drivers/i2c] Error 2
    make: *** [drivers] Error 2

    Signed-off-by: Balaji T K
    Signed-off-by: Ben Dooks

    Balaji T K
     
  • When runtime PM is enabled, each OMAP i2c device is suspended after
    each i2c xfer. However, there are two cases when the static suspend
    methods must be used to ensure the devices are suspended:

    1) runtime PM is disabled, either at compile time or dynamically
    via /sys/devices/.../power/control.
    2) an i2c client driver uses i2c during it's suspend callback, thus
    leaving the i2c driver active (NOTE: runtime suspend transitions are
    disabled during system suspend, so i2c activity during system
    suspend will runtime resume the device, but not runtime (re)suspend it.)

    Since the actual work to suspend the device is handled by the
    subsytem, call the bus methods to take care of it.

    NOTE: This takes care of a known suspend problem on OMAP3 where the
    TWL RTC driver does i2c xfers during its suspend path leaving the i2c
    driver in an active state (since runtime suspend transistions are
    disabled.)

    Signed-off-by: Kevin Hilman
    Signed-off-by: Ben Dooks

    Kevin Hilman
     
  • Use strlcpy instead of strncpy.

    Signed-off-by: Wolfram Sang
    Cc: Linus Walleij
    Cc: Ben Dooks
    Signed-off-by: Ben Dooks

    Wolfram Sang
     
  • * 'urgent' of git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia-2.6:
    pcmcia: re-enable Zoomed Video support
    cm4000_cs: Fix undefined ops warning
    pcmcia vs. MECR on pxa25x/sa1111
    drivers/char/pcmcia/ipwireless/main.c: Convert release_resource to release_region/release_mem_region

    Linus Torvalds
     
  • …git/tip/linux-2.6-tip

    * 'irq-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
    genirq: Disable the SHIRQ_DEBUG call in request_threaded_irq for now
    genirq: Prevent access beyond allocated_irqs bitmap

    Linus Torvalds
     
  • …/git/tip/linux-2.6-tip

    * 'perf-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
    perf: Fix throttle logic
    perf, x86: P4 PMU: Fix spurious NMI messages

    Linus Torvalds
     
  • * 'fix/asoc' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6:
    ASoC: Ensure supplies are maintained for force enabled widgets
    ASoC: WM8994: Improve playback robustness
    ASoC: WM8994: Improve robustness in some use cases
    ASoC: WM8903: Fix mic detection enable logic
    ASoC: WM8903: Fix mic detection register definitions
    ASoC: CX20442: fix wrong reg_cache_default content
    ASoC: Sync initial widget state with hardware

    Linus Torvalds
     
  • Building with CONFIG_KERNEL_XZ results in the following:

    # Untracked files:
    # (use "git add ..." to include in what will be committed)
    #
    # arch/x86/boot/compressed/vmlinux.bin.xz

    So ignore xz-compressed files at the top level like we already do for
    other compression types.

    Signed-off-by: Romain Francoise
    Signed-off-by: Linus Torvalds

    Romain Francoise
     

22 Feb, 2011

27 commits

  • Linus Torvalds
     
  • * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ecryptfs/ecryptfs-2.6:
    eCryptfs: Copy up lower inode attrs in getattr
    ecryptfs: read on a directory should return EISDIR if not supported
    eCryptfs: Handle NULL nameidata pointers
    eCryptfs: Revert "dont call lookup_one_len to avoid NULL nameidata"

    Linus Torvalds
     
  • The current code does not follow Intel documentation: It misses some things
    and does other, undocumented things. This causes wrong backlight values in
    certain conditions. Instead of adding tricky code handling badly documented
    and rare corner cases, don't handle combination mode specially at all. This
    way PCI_LBPC is never touched and weird things shouldn't happen.

    If combination mode is enabled, then the only downside is that changing the
    brightness has a greater granularity (the LBPC value), but LBPC is at most
    254 and the maximum is in the thousands, so this is no real functional loss.

    A potential problem with not handling combined mode is that a brightness of
    max * PCI_LBPC is not bright enough. However, this is very unlikely because
    from the documentation LBPC seems to act as a scaling factor and doesn't look
    like it's supposed to be changed after boot. The value at boot should always
    result in a bright enough screen.

    IMPORTANT: However, although usually the above is true, it may not be when
    people ran an older (2.6.37) kernel which messed up the LBPC register, and
    they are unlucky enough to have a BIOS that saves and restores the LBPC value.
    Then a good kernel may seem to not work: Max brightness isn't bright enough.
    If this happens people should boot back into the old kernel, set brightness
    to the maximum, and then reboot. After that everything should be fine.

    For more information see the below links. This fixes bugs:

    http://bugzilla.kernel.org/show_bug.cgi?id=23472
    http://bugzilla.kernel.org/show_bug.cgi?id=25072

    Signed-off-by: Indan Zupancic
    Tested-by: Alex Riesen
    Signed-off-by: Linus Torvalds

    Indan Zupancic
     
  • We force particular alignment when we generate attribute structures
    when generation MODULE_VERSION() data and we need to make sure that
    this alignment is followed when we iterate over these structures,
    otherwise we may crash on platforms whose natural alignment is not
    sizeof(void *), such as m68k.

    Reported-by: Geert Uytterhoeven
    Signed-off-by: Dmitry Torokhov
    [ There are more issues here, but the fixes are incredibly ugly - Linus ]
    Signed-off-by: Linus Torvalds

    Dmitry Torokhov
     
  • * 'for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mjg59/platform-drivers-x86:
    dell-laptop: Toggle the unsupported hardware killswitch
    thinkpad_acpi: Always report scancodes for hotkeys
    acer-wmi: Fix capitalisation of GUID
    platform/x86: ideapad-laptop depends on INPUT
    platform: x86: acer-wmi: world-writable sysfs threeg file
    platform: x86: asus_acpi: world-writable procfs files
    platform: x86: tc1100-wmi: world-writable sysfs wireless and jogdial files
    platform-drivers: x86: pmic: Use request_irq instead of chained handler
    platform-drivers: x86: pmic: Use irq_chip buslock mechanism
    platform-drivers: x86: Convert pmic to new irq_chip functions
    platform-drivers: x86: pmic: Fix up bogus irq hackery

    Linus Torvalds
     
  • * 'rc-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild-2.6:
    fixdep: Do not record dependency on the source file itself

    Linus Torvalds
     
  • Add fs/eventfd.c to filesystems docbook.
    Make typo corrections in fs/eventfd.c.

    Signed-off-by: Randy Dunlap
    Cc: Davide Libenzi
    Signed-off-by: Linus Torvalds

    Randy Dunlap
     
  • Update the "log_buf_len" description to use [KMG] syntax for the
    buffer size.

    Signed-off-by: Randy Dunlap
    Signed-off-by: Linus Torvalds

    Randy Dunlap
     
  • The '[KMG]' suffix is commonly described after a number of kernel
    parameter values documentation. Explicitly state its semantics.

    Signed-off-by: Ahmed S. Darwish
    Signed-off-by: Randy Dunlap
    Signed-off-by: Linus Torvalds

    Ahmed S. Darwish
     
  • Complete the crashkernel= kernel parameter documentation.

    Signed-off-by: Ahmed S. Darwish
    Acked-by: Simon Horman
    Acked-by: Vivek Goyal
    Signed-off-by: Randy Dunlap
    Signed-off-by: Linus Torvalds

    Ahmed S. Darwish
     
  • * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client:
    ceph: keep reference to parent inode on ceph_dentry
    ceph: queue cap_snaps once per realm
    libceph: fix socket write error handling
    libceph: fix socket read error handling

    Linus Torvalds
     
  • …git/kgene/linux-samsung

    * 's5p-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung:
    ARM: S5PV210: Fix regulator names
    ARM: S5PV210: Update max8998_platform_data
    ARM: SAMSUNG: Drop exporting s3c24xx_ts_set_platdata
    ARM: S5P: Fix end address in memory resource information for UART devices
    ARM: S5P64X0: Cleanup map.h file
    ARM: S5P6442: Cleanup map.h file
    ARM: S5PC100: Clenaup map.h file
    ARM: S5PV210: Cleanup map.h file
    ARM: S5PV310: Cleanup map.h file

    Linus Torvalds
     
  • * git://git.kernel.org/pub/scm/linux/kernel/git/sfrench/cifs-2.6:
    [CIFS] update cifs version
    cifs: Fix regression in LANMAN (LM) auth code
    cifs: fix handling of scopeid in cifs_convert_address

    Linus Torvalds
     
  • * 'fixes' of master.kernel.org:/home/rmk/linux-2.6-arm:
    ARM: 6745/1: kprobes insn decoding fix
    ARM: tlb: move noMMU tlb_flush() to asm/tlb.h
    ARM: tlb: delay page freeing for SMP and ARMv7 CPUs
    ARM: Keep exit text/data around for SMP_ON_UP
    ARM: Ensure predictable endian state on signal handler entry
    ARM: 6740/1: Place correctly notes section in the linker script
    ARM: 6700/1: SPEAr: Correct SOC config base address for spear320
    ARM: 6722/1: SPEAr: sp810: switch to slow mode before reset
    ARM: 6712/1: SPEAr: replace readl(), writel() with relaxed versions in uncompress.h
    ARM: 6720/1: SPEAr: Append UL to VMALLOC_END
    ARM: 6676/1: Correct the cpu_architecture() function for ARMv7
    ARM: 6739/1: update .gitignore for boot/compressed
    ARM: 6743/1: errata: interrupted ICALLUIS may prevent completion of broadcasted operation
    ARM: 6742/1: pmu: avoid setting IRQ affinity on UP systems
    ARM: 6741/1: errata: pl310 cache sync operation may be faulty

    Linus Torvalds
     
  • * 'for-linus' of git://git390.marist.edu/pub/scm/linux-2.6:
    [S390] net: provide architecture specific NET_SKB_PAD
    [S390] atomic: use inline asm
    [S390] correct ipl parameter block safe guard
    [S390] atomic: use ACCESS_ONCE() for atomic_read()
    [S390] dasd: correct device table

    Linus Torvalds
     
  • Update version to 1.71 so we can more easily spot modules with the last two fixes

    Signed-off-by: Steve French

    Steve French
     
  • It is found on Dell Inspiron 1018 that the firmware reports that the hardware
    killswitch is not supported. This makes the rfkill key not functional.

    This patch forces the driver to toggle the firmware rfkill status in the case
    that the hardware killswitch is indicated as unsupported by the firmware.

    Signed-off-by: Keng-Yu Lin
    Tested-by: Alessio Igor Bogani
    Signed-off-by: Matthew Garrett

    Keng-Yu Lin
     
  • Some thinkpad hotkeys report key codes like KEY_FN_F8 when something
    like KEY_VOLUMEDOWN is desired. Always provide the scan codes in
    addition to the key codes to assist with debugging these issues. Also
    send the scan code before the key code to match what other drivers do,
    as some userspace utilities expect this ordering.

    Signed-off-by: Seth Forshee
    Signed-off-by: Matthew Garrett

    Seth Forshee
     
  • 6AF4F258-B401-42fd-BE91-3D4AC2D7C0D3 needs to be
    6AF4F258-B401-42FD-BE91-3D4AC2D7C0D3 to match the hardware alias.

    Signed-off-by: Matthew Garrett
    Acked-by: Carlos Corbacho
    Cc: stable@kernel.org

    Matthew Garrett
     
  • Most platform/x86 drivers that use INPUT_SPARSEKMAP also depend on INPUT,
    so do the same for ideapad-laptop. This fixes a kconfig warning and
    subsequent build errors when CONFIG_INPUT is disabled.

    warning: (ACER_WMI && ASUS_LAPTOP && DELL_WMI && HP_WMI && PANASONIC_LAPTOP && IDEAPAD_LAPTOP && EEEPC_LAPTOP && EEEPC_WMI && MSI_WMI && TOPSTAR_LAPTOP && ACPI_TOSHIBA) selects INPUT_SPARSEKMAP which has unmet direct dependencies (!S390 && INPUT)

    ERROR: "input_free_device" [drivers/platform/x86/ideapad-laptop.ko] undefined!
    ERROR: "input_register_device" [drivers/platform/x86/ideapad-laptop.ko] undefined!
    ERROR: "sparse_keymap_setup" [drivers/platform/x86/ideapad-laptop.ko] undefined!
    ERROR: "input_allocate_device" [drivers/platform/x86/ideapad-laptop.ko] undefined!
    ERROR: "input_unregister_device" [drivers/platform/x86/ideapad-laptop.ko] undefined!
    ERROR: "sparse_keymap_free" [drivers/platform/x86/ideapad-laptop.ko] undefined!
    ERROR: "sparse_keymap_report_event" [drivers/platform/x86/ideapad-laptop.ko] undefined!

    Signed-off-by: Randy Dunlap
    Cc: David Woodhouse
    Cc: Matthew Garrett
    Cc: platform-driver-x86@vger.kernel.org
    Signed-off-by: Matthew Garrett

    Randy Dunlap
     
  • Don't allow everybody to write to hardware registers.

    Signed-off-by: Vasiliy Kulikov
    Signed-off-by: Matthew Garrett

    Vasiliy Kulikov
     
  • Don't allow everybody to change ACPI settings. The comment says that it
    is done deliberatelly, however, the comment before disp_proc_write()
    says that at least one of these setting is experimental.

    Signed-off-by: Vasiliy Kulikov
    Signed-off-by: Matthew Garrett

    Vasiliy Kulikov
     
  • Don't allow everybody to change WMI settings.

    Signed-off-by: Vasiliy Kulikov
    Signed-off-by: Matthew Garrett

    Vasiliy Kulikov
     
  • There is no need to install a chained handler for this hardware. This
    is a plain x86 IOAPIC interrupt which is handled by the core code
    perfectly fine. There is nothing special about demultiplexing these
    gpio interrupts which justifies a custom hack. Replace it by a plain
    old interrupt handler installed with request_irq. That makes the code
    agnostic about the underlying primary interrupt hardware. The overhead
    for this is minimal, but it gives us the advantage of accounting,
    balancing and to detect interrupt storms. gpio interrupts are not
    really that performance critical.

    Patch fixups from akpm

    Signed-off-by: Thomas Gleixner
    Signed-off-by: Matthew Garrett
    Signed-off-by: Andrew Morton

    Thomas Gleixner
     
  • LANMAN response length was changed to 16 bytes instead of 24 bytes.
    Revert it back to 24 bytes.

    Signed-off-by: Shirish Pargaonkar
    CC: stable@kernel.org
    Signed-off-by: Steve French

    Shirish Pargaonkar
     
  • The lower filesystem may do some type of inode revalidation during a
    getattr call. eCryptfs should take advantage of that by copying the
    lower inode attributes to the eCryptfs inode after a call to
    vfs_getattr() on the lower inode.

    I originally wrote this fix while working on eCryptfs on nfsv3 support,
    but discovered it also fixed an eCryptfs on ext4 nanosecond timestamp
    bug that was reported.

    https://bugs.launchpad.net/bugs/613873

    Cc:
    Signed-off-by: Tyler Hicks

    Tyler Hicks
     
  • read() calls against a file descriptor connected to a directory are
    incorrectly returning EINVAL rather than EISDIR:

    [EISDIR]
    [XSI] [Option Start] The fildes argument refers to a directory and the
    implementation does not allow the directory to be read using read()
    or pread(). The readdir() function should be used instead. [Option End]

    This occurs because we do not have a .read operation defined for
    ecryptfs directories. Connect this up to generic_read_dir().

    BugLink: http://bugs.launchpad.net/bugs/719691
    Signed-off-by: Andy Whitcroft
    Signed-off-by: Tyler Hicks

    Andy Whitcroft