Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tag: v2.6.29-rc8
Commits on Mar 13, 2009
  1. @torvalds

    Linus 2.6.29-rc8

    torvalds authored
  2. @torvalds

    bitmap: fix end condition in bitmap_find_free_region

    torvalds authored
    Guennadi Liakhovetski noticed that the end condition for the loop in
    bitmap_find_free_region() is wrong, and the "return if error" was also
    using the wrong conditional that would only trigger if the bitmap was an
    exact multiple of the allocation size, which is not necessarily the case
    with dma_alloc_from_coherent().
    
    Such a failure would end up in bitmap_find_free_region() accessing
    beyond the end of the bitmap.
    
    Reported-by: Guennadi Liakhovetski <lg@denx.de>
    Cc: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Commits on Mar 12, 2009
  1. @torvalds

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-fixes

    torvalds authored
    * git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild-fixes:
      kbuild: remove unused -r option for module-init-tool depmod
      kbuild: fix 'make rpm' when CONFIG_LOCALVERSION_AUTO=y and using SCM tree
      kbuild: fix mkspec to cleanup RPM_BUILD_ROOT
      kbuild: fix C libary confusion in unifdef.c due to getline()
  2. @torvalds

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-f…

    torvalds authored
    …or-linus
    
    * git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-for-linus:
      cpumask: mm_cpumask for accessing the struct mm_struct's cpu_vm_mask.
      cpumask: tsk_cpumask for accessing the struct task_struct's cpus_allowed.
  3. @torvalds

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/pkl/squashfs-linus

    torvalds authored
    * git://git.kernel.org/pub/scm/linux/kernel/git/pkl/squashfs-linus:
      Squashfs: Valid filesystems are flagged as bad by the corrupted fs patch
  4. @torvalds

    Merge branch 'hwmon-for-linus' of git://jdelvare.pck.nerim.net/jdelva…

    torvalds authored
    …re-2.6
    
    * 'hwmon-for-linus' of git://jdelvare.pck.nerim.net/jdelvare-2.6:
      hwmon: (f75375s) Remove unnecessary and confusing initialization
      hwmon: (it87) Properly decode -128 degrees C temperature
      hwmon: (lm90) Document support for the MAX6648/6692 chips
      hwmon: (abituguru3) Fix I/O error handling
  5. @torvalds

    trivial: fix bad links in the ext2 and ext3 documentation

    Jody McIntyre authored torvalds committed
    Trivial patch to fix bad links in the ext2 and ext3 documentation.
    
    Signed-off-by: Jody McIntyre <scjody@sun.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  6. @torvalds

    Merge branch 'fixes-20090312' of git://git.kernel.org/pub/scm/linux/k…

    torvalds authored
    …ernel/git/willy/pci
    
    * 'fixes-20090312' of git://git.kernel.org/pub/scm/linux/kernel/git/willy/pci:
      PCIe: portdrv: call pci_disable_device during remove
      pci: Fix typo in message while disabling HT MSI mapping
      pci: don't disable too many HT MSI mapping
      powerpc/pseries: The RPA PCI hotplug driver depends on EEH
      PCIe: AER: during disable, check subordinate before walking
      PCI: Add PCI quirk to disable L0s ASPM state for 82575 and 82598
  7. @torvalds

    RDMA/nes: Don't allow userspace QPs to use STag zero

    Faisal Latif authored torvalds committed
    STag zero is a special STag that allows consumers to access any bus
    address without registering memory.  The nes driver unfortunately
    allows STag zero to be used even with QPs created by unprivileged
    userspace consumers, which means that any process with direct verbs
    access to the nes device can read and write any memory accessible to
    the underlying PCI device (usually any memory in the system).  Such
    access is usually given for cluster software such as MPI to use, so
    this is a local privilege escalation bug on most systems running this
    driver.
    
    The driver was using STag zero to receive the last streaming mode
    data; to allow STag zero to be disabled for unprivileged QPs, the
    driver now registers a special MR for this data.
    
    Cc: <stable@kernel.org>
    Signed-off-by: Faisal Latif <faisal.latif@intel.com>
    Signed-off-by: Roland Dreier <rolandd@cisco.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  8. @torvalds

    fs: new inode i_state corruption fix

    Nick Piggin authored torvalds committed
    There was a report of a data corruption
    http://lkml.org/lkml/2008/11/14/121.  There is a script included to
    reproduce the problem.
    
    During testing, I encountered a number of strange things with ext3, so I
    tried ext2 to attempt to reduce complexity of the problem.  I found that
    fsstress would quickly hang in wait_on_inode, waiting for I_LOCK to be
    cleared, even though instrumentation showed that unlock_new_inode had
    already been called for that inode.  This points to memory scribble, or
    synchronisation problme.
    
    i_state of I_NEW inodes is not protected by inode_lock because other
    processes are not supposed to touch them until I_LOCK (and I_NEW) is
    cleared.  Adding WARN_ON(inode->i_state & I_NEW) to sites where we modify
    i_state revealed that generic_sync_sb_inodes is picking up new inodes from
    the inode lists and passing them to __writeback_single_inode without
    waiting for I_NEW.  Subsequently modifying i_state causes corruption.  In
    my case it would look like this:
    
    CPU0                            CPU1
    unlock_new_inode()              __sync_single_inode()
     reg <- inode->i_state
     reg -> reg & ~(I_LOCK|I_NEW)   reg <- inode->i_state
     reg -> inode->i_state          reg -> reg | I_SYNC
                                    reg -> inode->i_state
    
    Non-atomic RMW on CPU1 overwrites CPU0 store and sets I_LOCK|I_NEW again.
    
    Fix for this is rather than wait for I_NEW inodes, just skip over them:
    inodes concurrently being created are not subject to data integrity
    operations, and should not significantly contribute to dirty memory
    either.
    
    After this change, I'm unable to reproduce any of the added warnings or
    hangs after ~1hour of running.  Previously, the new warnings would start
    immediately and hang would happen in under 5 minutes.
    
    I'm also testing on ext3 now, and so far no problems there either.  I
    don't know whether this fixes the problem reported above, but it fixes a
    real problem for me.
    
    Cc: "Jorge Boncompte [DTI2]" <jorge@dti2.net>
    Reported-by: Adrian Hunter <ext-adrian.hunter@nokia.com>
    Cc: Jan Kara <jack@suse.cz>
    Cc: <stable@kernel.org>
    Signed-off-by: Nick Piggin <npiggin@suse.de>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  9. @kosaki @torvalds

    memcg: use correct scan number at reclaim

    kosaki authored torvalds committed
    Even when page reclaim is under mem_cgroup, # of scan page is determined by
    status of global LRU. Fix that.
    
    Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
    Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
    Cc: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
    Cc: Balbir Singh <balbir@in.ibm.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  10. @broonie @torvalds

    mfd: add support for WM8351 revision B

    broonie authored torvalds committed
    No software visible difference from revision A.
    
    Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
    Cc: Samuel Ortiz <sameo@openedhand.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  11. @mspang @torvalds

    acer-wmi: fix regression in backlight detection

    mspang authored torvalds committed
    Currently we disable the Acer WMI backlight device if there is no ACPI
    backlight device.  As a result, we end up with no backlight device at all.
     We should instead disable it if there is an ACPI device, as the other
    laptop drivers do.  This regression was introduced in febf2d9 ("Acer-WMI:
    fingers off backlight if video.ko is serving this functionality").
    
    Each laptop driver with backlight support got a similar change around
    febf2d9.  The changes to the other drivers look correct; see e.g.
    a598c82 for a similar but correct change.  The regression is also in
    2.6.28.
    
    Signed-off-by: Michael Spang <mspang@csclub.uwaterloo.ca>
    Acked-by: Thomas Renninger <trenn@suse.de>
    Cc: Zhang Rui <rui.zhang@intel.com>
    Cc: Andi Kleen <ak@linux.intel.com>
    Cc: Carlos Corbacho <carlos@strangeworlds.co.uk>
    Cc: Len Brown <len.brown@intel.com>
    Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
    Cc: <stable@kernel.org>		[2.6.28.x]
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  12. @torvalds

    mmc: s3cmci: fix s3c2410_dma_config() arguments.

    Ben Dooks authored torvalds committed
    The s3cmci driver is calling s3c2410_dma_config with incorrect data for
    the DCON register.  The S3C2410_DCON_HWTRIG is implicit in the channel
    configuration and the device selection of S3C2410_DCON_CH0_SDI is
    incorrect as the DMA system may not select channel 0.
    
    Signed-off-by: Ben Dooks <ben@simtec.co.uk>
    Acked-by: Pierre Ossman <drzeus@drzeus.cx>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  13. @torvalds

    MAINTAINERS: downgrade support for man-pages

    Michael Kerrisk authored torvalds committed
    Unfortunately, Linux Foundation funding for my work on
    man-pages/testing/doc under the auspices of the LF documentation
    fellowship unfortunately ran out a short while ago (after earlier attempts
    to seek funding, only Google stepped forward with a bit of further funding
    for the position), so the patch below acknowledges something closer to
    reality.
    
    Unfortunately, there will (probably very) soon be a further downgrade from
    "Maintained" to "Odd Fixes" or "Orphan", unless some funding miracle
    occurs.  So, if anyone is looking to become man-pages maintainer, there
    may soon be an opening (okay, don't trample me in the rush ;-).)
    
    Signed-off-by: Michael Kerrisk <mtk.manpages@googlemail.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  14. @zonque @torvalds

    ds2760_battery.c: fix division by zero

    zonque authored torvalds committed
    The 'battery remaining capacity' calculation in
    drivers/power/ds2760_battery.c lacks a parameter check to a division
    operation which causes the kernel to oops on my board.
    
    [   21.233750] Division by zero in kernel.
    [   21.237646] [<c002955c>] (__div0+0x0/0x20) from [<c012561c>] (Ldiv0+0x8/0x10)
    [   21.244816] [<c01bef34>] (ds2760_battery_read_status+0x0/0x2a4) from [<c01bf3a4>] (ds2760_battery_get_property+0x30/0xdc)
    [   21.255803]  r8:c03a22c0 r7:c7886100 r6:00000009 r5:c782fe7c r4:c7886084
    [   21.262518] [<c01bf374>] (ds2760_battery_get_property+0x0/0xdc) from [<c01bde98>] (power_supply_show_property+0x48/0x114)
    [   21.273480]  r6:c7996000 r5:00000009 r4:00000000
    [   21.278111] [<c01bde50>] (power_supply_show_property+0x0/0x114) from [<c01be158>] (power_supply_uevent+0x188/0x280)
    [   21.288537]  r8:00000001 r7:c7886100 r6:c7996000 r5:000000b4 r4:00000000
    [   21.295222] [<c01bdfd0>] (power_supply_uevent+0x0/0x280) from [<c015c664>] (dev_uevent+0xd4/0x10c)
    [   21.304199] [<c015c590>] (dev_uevent+0x0/0x10c) from [<c0128440>] (kobject_uevent_env+0x180/0x390)
    [   21.313170]  r5:00000000 r4:c78860ac
    [   21.316725] [<c01282c0>] (kobject_uevent_env+0x0/0x390) from [<c0128664>] (kobject_uevent+0x14/0x18)
    [   21.325850] [<c0128650>] (kobject_uevent+0x0/0x18) from [<c01bdc34>] (power_supply_changed_work+0x5c/0x70)
    [   21.335506] [<c01bdbd8>] (power_supply_changed_work+0x0/0x70) from [<c004d290>] (run_workqueue+0xbc/0x144)
    [   21.345167]  r4:c7812040
    [   21.347716] [<c004d1d4>] (run_workqueue+0x0/0x144) from [<c004d94c>] (worker_thread+0xa8/0xbc)
    [   21.356296]  r7:c7812040 r6:c7820b00 r5:c782ffa4 r4:c7812048
    [   21.361957] [<c004d8a4>] (worker_thread+0x0/0xbc) from [<c0051008>] (kthread+0x5c/0x94)
    [   21.369971]  r7:00000000 r6:c004d8a4 r5:c7812040 r4:c782e000
    [   21.375612] [<c0050fac>] (kthread+0x0/0x94) from [<c00403d0>] (do_exit+0x0/0x688)
    
    Signed-off-by: Daniel Mack <daniel@caiaq.de>
    Cc: Szabolcs Gyurko <szabolcs.gyurko@tlt.hu>
    Acked-by: Matt Reimer <mreimer@vpop.net>
    Acked-by: Anton Vorontsov <cbou@mail.ru>
    Cc: David Woodhouse <dwmw2@infradead.org>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  15. @torvalds

    vfs: add missing unlock in sget()

    Li Zefan authored torvalds committed
    In sget(), destroy_super(s) is called with s->s_umount held, which makes
    lockdep unhappy.
    
    Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
    Cc: Al Viro <viro@ZenIV.linux.org.uk>
    Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Cc: Paul Menage <menage@google.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  16. @utrace @torvalds

    pipe_rdwr_fasync: fix the error handling to prevent the leak/crash

    utrace authored torvalds committed
    If the second fasync_helper() fails, pipe_rdwr_fasync() returns the error
    but leaves the file on ->fasync_readers.
    
    This was always wrong, but since 233e70f
    "saner FASYNC handling on file close" we have the new problem.  Because in
    this case setfl() doesn't set FASYNC bit, __fput() will not do
    ->fasync(0), and we leak fasync_struct with ->fa_file pointing to the
    freed file.
    
    Signed-off-by: Oleg Nesterov <oleg@redhat.com>
    Cc: Al Viro <viro@ZenIV.linux.org.uk>
    Cc: Andi Kleen <andi@firstfloor.org>
    Cc: Jonathan Corbet <corbet@lwn.net>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  17. @zonque @torvalds

    drivers/w1/masters/w1-gpio.c: fix read_bit()

    zonque authored torvalds committed
    W1 master implementations are expected to return 0 or 1 from their
    read_bit() function.  However, not all platforms do return these values
    from gpio_get_value() - namely PXAs won't.  Hence the w1 gpio-master needs
    to break the result down to 0 or 1 itself.
    
    Signed-off-by: Daniel Mack <daniel@caiaq.de>
    Cc: Ville Syrjala <syrjala@sci.fi>
    Cc: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
    Cc: David Brownell <david-b@pacbell.net>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  18. @torvalds

    uml: fix WARNING: vmlinux: 'memcpy' exported twice

    akpm@linux-foundation.org authored torvalds committed
    Fix the following warning on x86_64:
    
    LD vmlinux.o
    MODPOST vmlinux.o
    WARNING: vmlinux: 'memcpy' exported twice. Previous export was in vmlinux
    
    For x86_64, this symbol is already exported from arch/um/sys-x86_64/ksyms.c.
    
    Reported-by: Boaz Harrosh <bharrosh@panasas.com>
    Signed-off-by: WANG Cong <xiyou.wangcong@gmail.com>
    Tested-by: Boaz Harrosh <bharrosh@panasas.com>
    Cc: Jeff Dike <jdike@addtoit.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  19. @rd235 @torvalds

    UML on UML fixed: it did not start

    rd235 authored torvalds committed
    It is currently impossible to run a user-mode linux machine inside another
    user-mode linux (UML on UML).  It breaks after a few instructions.  When
    it tries to check whether SYSEMU is installed (the inner) UML receives an
    inconsistent result (from the outer UML).
    
    This is the output of a broken attempt:
    $ ./linux mem=256m ubd0=cow
    Locating the bottom of the address space ... 0x0
    Locating the top of the address space ... 0xc0000000
    Core dump limits :
            soft - 0
            hard - NONE
    Checking that ptrace can change system call numbers...OK
    Checking ptrace new tags for syscall emulation...unsupported
    Checking syscall emulation patch for ptrace...check_sysemu : expected SIGTRAP, got status = 256
    $
    
    The problem is the following:
    
    PTRACE_SYSCALL/SINGLESTEP is currently managed inside arch_ptrace for ARCH=um.
    
    PTRACE_SYSEMU/SUSEMU_SINGLESTEP is not captured in arch_ptrace's switch,
    therefore it is erroneously passed back to ptrace_request (in
    kernel/ptrace).
    
    This simple patch simply forces ptrace to return an error on
    PTRACE_SYSEMU/SUSEMU_SINGLESTEP as it is unsupported on ARCH=um, and fixes
    the problem.
    
    [akpm@linux-foundation.org: coding-style fixes]
    Signed-off-by: Renzo Davoli <renzo@cs.unibo.it>
    Reviewed-by: WANG Cong <xiyou.wangcong@gmail.com>
    Cc: Jeff Dike <jdike@addtoit.com>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
  20. PCIe: portdrv: call pci_disable_device during remove

    Alex Chiang authored Matthew Wilcox committed
    The PCIe port driver calls pci_enable_device() during probe but
    never calls pci_disable_device() during remove.
    
    Cc: stable@kernel.org
    Signed-off-by: Alex Chiang <achiang@hp.com>
    Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
  21. pci: Fix typo in message while disabling HT MSI mapping

    Prakash Punnoor authored Matthew Wilcox committed
    "Enabling" should read "Disabling"
    
    Signed-off-by: Prakash Punnoor <prakash@punnoor.de>
    Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
  22. pci: don't disable too many HT MSI mapping

    Prakash Punnoor authored Matthew Wilcox committed
    Prakash's system needs MSI disabled on some bridges, but not all.
    This seems to be the minimal fix for 2.6.29, but should be replaced
    during 2.6.30.
    
    Signed-off-by: Prakash Punnoor <prakash@punnoor.de>
    Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
  23. @mpe

    powerpc/pseries: The RPA PCI hotplug driver depends on EEH

    mpe authored Matthew Wilcox committed
    The RPA PCI hotplug driver calls EEH routines, so should depend on
    EEH. Also PPC_PSERIES implies PPC64, so remove that.
    
    Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
    Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
  24. PCIe: AER: during disable, check subordinate before walking

    Alex Chiang authored Matthew Wilcox committed
    Commit 47a8b0cc (Enable PCIe AER only after checking firmware
    support) wants to walk the PCI bus in the remove path to disable
    AER, and calls pci_walk_bus for downstream bridges.
    
    Unfortunately, in the remove path, we remove devices and bridges
    in a depth-first manner, starting with the furthest downstream
    bridge and working our way backwards.
    
    The furthest downstream bridges will not have a dev->subordinate,
    and we hit a NULL deref in pci_walk_bus.
    
    Check for dev->subordinate first before attempting to walk the
    PCI hierarchy below us.
    
    Acked-by: Andrew Patterson <andrew.patterson@hp.com>
    Signed-off-by: Alex Chiang <achiang@hp.com>
    Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
  25. PCI: Add PCI quirk to disable L0s ASPM state for 82575 and 82598

    Alexander Duyck authored Matthew Wilcox committed
    This patch is intended to disable L0s ASPM link state for 82598 (ixgbe)
    parts due to the fact that it is possible to corrupt TX data when coming
    back out of L0s on some systems.  The workaround had been added for 82575
    (igb) previously, but did not use the ASPM api.  This quirk uses the ASPM
    api to prevent the ASPM subsystem from re-enabling the L0s state.
    
    Instead of adding the fix in igb to the ixgbe driver as well it was
    decided to move it into a pci quirk.  It is necessary to move the fix out
    of the driver and into a pci quirk in order to prevent the issue from
    occuring prior to driver load to handle the possibility of the device being
    passed to a VM via direct assignment.
    
    Signed-off-by: Alexander Duyck <alexander.h.duyck@intel.com>
    Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
    CC: Jesse Barnes <jbarnes@virtuousgeek.org>
    Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
  26. @torvalds

    Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-2.6

    torvalds authored
    * git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-2.6:
      sunhme: Fix qfe parent detection.
      sparc64: Fix lost interrupts on sun4u.
      sparc64: wait_event_interruptible_timeout may return -ERESTARTSYS
      jsflash: stop defining MAJOR_NR
  27. @torvalds

    Merge branch 'upstream' of git://ftp.linux-mips.org/pub/scm/upstream-…

    torvalds authored
    …linus
    
    * 'upstream' of git://ftp.linux-mips.org/pub/scm/upstream-linus:
      MIPS: IP27: Enable RAID5 module
      MIPS: TXx9: update defconfigs
      MIPS: NEC VR5500 processor support fixup
      MIPS: Fix build of non-CONFIG_SYSVIPC version of sys_32_ipc
  28. hwmon: (f75375s) Remove unnecessary and confusing initialization

    Andrew Klossner authored Jean Delvare committed
    f75375_probe calls i2c_get_clientdata to initialize the data pointer,
    but there isn't yet any client data to get, and the value is never
    used before the variable is assigned a new value seven lines later.
    
    The call doesn't hurt anything and wastes only a couple of cycles.
    The reason to fix it is because this module serves as an example to
    hackers writing new hwmon drivers, and this part of the example is
    confusing.
    
    Signed-off-by: Andrew Klossner <andrew@cesa.opbu.xerox.com>
    Signed-off-by: Jean Delvare <khali@linux-fr.org>
  29. hwmon: (it87) Properly decode -128 degrees C temperature

    Jean Delvare authored
    The it87 driver is reporting -128 degrees C as +128 degrees C.
    That's not a terribly likely temperature value but let's still
    get it right, especially when it simplifies the code.
    
    Signed-off-by: Jean Delvare <khali@linux-fr.org>
  30. hwmon: (lm90) Document support for the MAX6648/6692 chips

    Darrick J. Wong authored Jean Delvare committed
    Update documentation to prevent further confusion/duplication.
    
    Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
    Signed-off-by: Jean Delvare <khali@linux-fr.org>
  31. hwmon: (abituguru3) Fix I/O error handling

    Jean Delvare authored
    Fix a logic bug reported by Roel Kluin, by rewriting the error
    handling code in a clearer way.
    
    Signed-off-by: Jean Delvare <khali@linux-fr.org>
    Cc: Roel Kluin <roel.kluin@gmail.com>
    Acked-by: Alistair John Strachan <alistair@devzero.co.uk>
    Acked-by: Hans de Goede <hdegoede@redhat.com>
  32. @rustyrussell

    cpumask: mm_cpumask for accessing the struct mm_struct's cpu_vm_mask.

    rustyrussell authored
    This allows us to change the representation (to a dangling bitmap or
    cpumask_var_t) without breaking all the callers: they can use
    mm_cpumask() now and won't see a difference as the changes roll into
    linux-next.
    
    Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
  33. @rustyrussell

    cpumask: tsk_cpumask for accessing the struct task_struct's cpus_allo…

    rustyrussell authored
    …wed.
    
    This allows us to change the representation (to a dangling bitmap or
    cpumask_var_t) without breaking all the callers: they can use
    tsk_cpumask() now and won't see a difference as the changes roll into
    linux-next.
    
    Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Something went wrong with that request. Please try again.