Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Feb 5, 2013
  1. mailbox: call request_irq after mbox queues are allocated

    authored
    The mailbox startup code is enabling the interrupt even before
    any of the associated mailbox queues are allocated. A received
    mailbox message could could cause a kernel panic when the mailbox
    queues are dereferenced within the ISR.
    
    Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com>
    Signed-off-by: Suman Anna <s-anna@ti.com>
  2. mailbox: check for NULL nb in mailbox_put

    authored
    The mailbox_put function must check the notifier block for
    NULL before trying to unregister it.
    
    Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com>
    Signed-off-by: Suman Anna <s-anna@ti.com>
  3. mailbox/omap: check iomem resource before dereferencing it

    authored
    Add a NULL check for iomem resource in mailbox probe functions.
    
    Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com>
    Signed-off-by: Suman Anna <s-anna@ti.com>
  4. @ydrallap

    mailbox: create dbx500 mailbox driver

    ydrallap authored committed
    Add STEriccson DBX500 PRCM mailbox support.
    
    Signed-off-by: Loic Pallardy <loic.pallardy@st.com>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
  5. @ydrallap

    mailbox: add no_irq send message

    ydrallap authored committed
    For debug purpose, mailbox must be available when
    interrupts are disabled to collect dump information.
    
    Signed-off-by: Loic Pallardy <loic.pallardy@st.com>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
  6. @ydrallap

    mailbox: add IRQF_NO_SUSPEND flag

    ydrallap authored committed
    Coprocessor must be accessible during suspend transitions.
    
    Signed-off-by: Loic Pallardy <loic.pallardy@st.com>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
  7. @ydrallap

    mailbox: add shared memory mailbox type

    ydrallap authored committed
    Some mailboxes are made up of cross interrupts
    and associated shared memory.
    Shared memory mapping is fixed and cross interrupt/shared
    memory relation make impossible the use of virtio.
    Mailbox framework must be enough opened to support
    any kind of mailbox.
    
    Signed-off-by: Loic Pallardy <loic.pallardy@st.com>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
  8. @ydrallap

    mailbox: change protection mechanisms

    ydrallap authored committed
    TX: replace spin by mutex to release CPU
    during wait on mailbox resource.
    
    Signed-off-by: Loic Pallardy <loic.pallardy@st.com>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
  9. @ydrallap

    mailbox: change OMAP1&2 opened message adaptation

    ydrallap authored committed
    This patch change internal OMAP1&2 mailbox drivers
    behavior to use pdata field of mailbox_msg structure
    instead of header one which could be confusing.
    
    Signed-off-by: Loic Pallardy <loic.pallardy@st.com>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
  10. @ydrallap

    mailbox: create opened message type

    ydrallap authored committed
    Current message type is a u32 to fit HW fifo format.
    This should be extended to support any message exchanges
    and type of mailbox.
    
    Proposed structure owns the original u32 and an optional
    pointer on additional data.
    
    Adaptations made to remoteproc and tidspbridge drivers.
    
    Signed-off-by: Loic Pallardy <loic.pallardy@st.com>
    Signed-off-by: Omar Ramirez Luna <omar.ramirez@copitl.com>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Commits on Feb 4, 2013
  1. @ydrallap

    mailbox: rename omap_mbox in mailbox

    ydrallap authored committed
    In order to create a generic mailbox framework, functions
    and structures should be renamed in mailbox.
    
    Taking care of remoteproc and tidspbridge while at it.
    
    Signed-off-by: Loic Pallardy <loic.pallardy@st.com>
    Signed-off-by: Omar Ramirez Luna <omar.ramirez@copitl.com>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
  2. mailbox: split internal header from API header

    Omar Ramirez Luna authored committed
    Now internal structures can remain hidden to the user and just API
    related functions and defines are made available.
    
    Signed-off-by: Omar Ramirez Luna <omar.luna@linaro.org>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
  3. mailbox: OMAP: introduce mailbox framework

    Omar Ramirez Luna authored committed
    Actually moving it from plat-omap, as this framework/driver code is
    supposed to be under drivers/ folder. The framework should work with
    the current supported OMAP processors (OMAP1+) that have mailbox and
    can be used as a method of interprocessor communication.
    
    The mailbox hardware (in OMAP) uses a queued mailbox-interrupt mechanism
    that provides a communication channel between processors through a set of
    registers and their associated interrupt signals by sending and receiving
    messages.
    
    As part of the migration from plat and mach code:
    - Kconfig symbols have been renamed to build OMAP1 or OMAP2+ drivers.
    - mailbox.h has been changed from plat to a dedicated drivers/ folder.
    - soc.h has been changed for plat/cpu.h, since there are dependencies in
      the cpu_is_XXXX() macro.
    
    Module names have changed too, instead of mailbox_mach:
    - OMAP1: mailbox-omap1.ko
    - OMAP2+: mailbox-omap2.ko
    
    Signed-off-by: Omar Ramirez Luna <omar.luna@linaro.org>
    Acked-by: Tony Lindgren <tony@atomide.com>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
  4. ARM: OMAP2+: mbox: remove dependencies with soc.h

    authored
    The OMAP mailbox platform driver code has been cleaned up to
    remove the dependencies with soc.h in preparation for moving
    the mailbox code to drivers folder.
    
    The code relied on cpu_is_xxx/soc_is_xxx macros previously to
    pick the the right set of mailbox devices and register with the
    mailbox driver. This data is now represented in a concise format
    and moved to the respective omap_hwmod data files and published
    to the driver through the platform data.
    
    Signed-off-by: Suman Anna <s-anna@ti.com>
Commits on Feb 1, 2013
  1. @torvalds

    Linux 3.8-rc6

    torvalds authored
  2. @torvalds

    Merge tag 'dm-3.8-fixes-2' of git://git.kernel.org/pub/scm/linux/kern…

    torvalds authored
    …el/git/agk/linux-dm
    
    Pull more device-mapper fixes from Alasdair G Kergon:
     "A fix for stacked dm thin devices and a fix for the new dm WRITE SAME
      support."
    
    * tag 'dm-3.8-fixes-2' of git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-dm:
      dm: fix write same requests counting
      dm thin: fix queue limits stacking
Commits on Jan 31, 2013
  1. @torvalds

    Merge branch 'for-3.8/upstream-fixes' of git://git.kernel.org/pub/scm…

    torvalds authored
    …/linux/kernel/git/jikos/hid
    
    PullHID fixes from Jiri Kosina:
    
     - fix i2c-hid and hidraw interaction, by Benjamin Tissoires
    
     - a quirk to make a particular device (Formosa IR receiver) work
       properly, by Nicholas Santos
    
    * 'for-3.8/upstream-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid:
      HID: i2c-hid: fix i2c_hid_output_raw_report
      HID: usbhid: quirk for Formosa IR receiver
      HID: remove x bit from sensor doc
  2. @torvalds

    Merge tag 'nfs-for-3.8-4' of git://git.linux-nfs.org/projects/trondmy…

    torvalds authored
    …/linux-nfs
    
    Pull NFS client bugfixes from Trond Myklebust:
    
     - Error reporting in nfs_xdev_mount incorrectly maps all errors to
       ENOMEM
    
     - Fix an NFSv4 refcounting issue
    
     - Fix a mount failure when the server reboots during NFSv4 trunking
       discovery
    
     - NFSv4.1 mounts may need to run the lease recovery thread.
    
     - Don't silently fail setattr() requests on mountpoints
    
     - Fix a SUNRPC socket/transport livelock and priority queue issue
    
     - We must handle NFS4ERR_DELAY when resetting the NFSv4.1 session.
    
    * tag 'nfs-for-3.8-4' of git://git.linux-nfs.org/projects/trondmy/linux-nfs:
      NFSv4.1: Handle NFS4ERR_DELAY when resetting the NFSv4.1 session
      SUNRPC: When changing the queue priority, ensure that we change the owner
      NFS: Don't silently fail setattr() requests on mountpoints
      NFSv4.1: Ensure that nfs41_walk_client_list() does start lease recovery
      NFSv4: Fix NFSv4 trunking discovery
      NFSv4: Fix NFSv4 reference counting for trunked sessions
      NFS: Fix error reporting in nfs_xdev_mount
  3. @torvalds

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

    torvalds authored
    …ream-linus
    
    Pull MIPS updates from Ralf Baechle:
     "A number of fixes all across the MIPS tree.  No area is particularly
      standing out and things have cooled down quite nicely for a release."
    
    * 'upstream' of git://git.linux-mips.org/pub/scm/ralf/upstream-linus:
      MIPS: Function tracer: Fix broken function tracing
      mips: Move __virt_addr_valid() to a place for MIPS 64
      MIPS: Netlogic: Fix UP compilation on XLR
      MIPS: AR71xx: Fix AR71XX_PCI_MEM_SIZE
      MIPS: AR724x: Fix AR724X_PCI_MEM_SIZE
      MIPS: Lantiq: Fix cp0_perfcount_irq mapping
      MIPS: DSP: Fix DSP mask for registers.
      MIPS: Fix build failure by adding definition of pfn_pmd().
      MIPS: Octeon: Fix warning.
      MIPS: delay.c: Check BITS_PER_LONG instead of __SIZEOF_LONG__
      MIPS: PNX833x: Fix comment.
      MIPS: Add struct p_format to union mips_instruction.
      MIPS: Export <asm/break.h>.
      MIPS: BCM47xx: Enable SSB prerequisite SSB_DRIVER_PCICORE.
      MIPS: BCM47xx: Select GPIOLIB for BCMA on bcm47xx platform
      MIPS: vpe.c: Fix null pointer dereference in print arguments.
  4. @bentiss

    HID: i2c-hid: fix i2c_hid_output_raw_report

    bentiss authored Jiri Kosina committed
    i2c_hid_output_raw_report is used by hidraw to forward set_report requests.
    The current implementation of i2c_hid_set_report needs to take the
    report_id as an argument. The report_id is stored in the first byte
    of the buffer in argument of i2c_hid_output_raw_report.
    
    Not removing the report_id from the given buffer adds this byte 2 times
    in the command, leading to a non working command.
    
    Reported-by: Andrew Duggan <aduggan@synaptics.com>
    Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
    Signed-off-by: Jiri Kosina <jkosina@suse.cz>
  5. @alcooper @ralfbaechle

    MIPS: Function tracer: Fix broken function tracing

    alcooper authored ralfbaechle committed
    Function tracing is currently broken for all 32 bit MIPS platforms.
    When tracing is enabled, the kernel immediately hangs on boot.
    This is a result of commit b732d43
    that changes the kernel/trace/Kconfig file so that is no longer
    forces FRAME_POINTER when FUNCTION_TRACING is enabled.
    
    MIPS frame pointers are generally considered to be useless because
    they cannot be used to unwind the stack. Unfortunately the MIPS
    function tracing code has bugs that are masked by the use of frame
    pointers. This commit fixes the bugs so that MIPS frame pointers
    don't need to be enabled.
    
    The bugs are a result of the odd calling sequence used to call the trace
    routine. This calling sequence is inserted into every traceable function
    when the tracing CONFIG option is enabled. This sequence is generated
    for 32bit MIPS platforms by the compiler via the "-pg" flag.
    
    Part of the sequence is "addiu sp,sp,-8" in the delay slot after every
    call to the trace routine "_mcount" (some legacy thing where 2 arguments
    used to be pushed on the stack). The _mcount routine is expected to
    adjust the sp by +8 before returning.  So when not disabled, the original
    jalr and addiu will be there, so _mcount has to adjust sp.
    
    The problem is that when tracing is disabled for a function, the
    "jalr _mcount" instruction is replaced with a nop, but the
    "addiu sp,sp,-8" is still executed and the stack pointer is left
    trashed. When frame pointers are enabled the problem is masked
    because any access to the stack is done through the frame
    pointer and the stack pointer is restored from the frame pointer when
    the function returns.
    
    This patch writes two nops starting at the address of the "jalr _mcount"
    instruction whenever tracing is disabled. This means that the
    "addiu sp,sp.-8" will be converted to a nop along with the "jalr".  When
    disabled, there will be two nops.
    
    This is SMP safe because the first time this happens is during
    ftrace_init() which is before any other processor has been started.
    Subsequent calls to enable/disable tracing when other CPUs ARE running
    will still be safe because the enable will only change the first nop
    to a "jalr" and the disable, while writing 2 nops, will only be changing
    the "jalr". This patch also stops using stop_machine() to call the
    tracer enable/disable routines and calls them directly because the
    routines are SMP safe.
    
    When the kernel first boots we have to be able to handle the gcc
    generated jalr, addui sequence until ftrace_init gets a chance to run
    and change the sequence. At this point mcount just adjusts the stack
    and returns. When ftrace_init runs, we convert the jalr/addui to nops.
    Then whenever tracing is enabled we convert the first nop to a "jalr
    mcount+8". The mcount+8 entry point skips the stack adjust.
    
    [ralf@linux-mips.org: Folded in  Steven Rostedt's build fix.]
    
    Signed-off-by: Al Cooper <alcooperx@gmail.com>
    Cc: rostedt@goodmis.org
    Cc: ddaney.cavm@gmail.com
    Cc: linux-mips@linux-mips.org
    Cc: linux-kernel@vger.kernel.org
    Patchwork: https://patchwork.linux-mips.org/patch/4806/
    Patchwork: https://patchwork.linux-mips.org/patch/4841/
    Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
  6. dm: fix write same requests counting

    Alasdair G Kergon authored
    When processing write same requests, fix dm to send the configured
    number of WRITE SAME requests to the target rather than the number of
    discards, which is not always the same.
    
    Device-mapper WRITE SAME support was introduced by commit
    23508a9 ("dm: add WRITE SAME support").
    
    Signed-off-by: Alasdair G Kergon <agk@redhat.com>
    Acked-by: Mike Snitzer <snitzer@redhat.com>
  7. @rostedt @ralfbaechle

    mips: Move __virt_addr_valid() to a place for MIPS 64

    rostedt authored ralfbaechle committed
    Commit d3ce884 "MIPS: Fix modpost error in modules attepting to use
    virt_addr_valid()" moved __virt_addr_valid() from a macro in a header
    file to a function in ioremap.c. But ioremap.c is only compiled for MIPS
    32, and not for MIPS 64.
    
    When compiling for my yeeloong2, which supposedly supports hibernation,
    which compiles kernel/power/snapshot.c which calls virt_addr_valid(), I
    got this error:
    
      LD      init/built-in.o
    kernel/built-in.o: In function `memory_bm_free':
    snapshot.c:(.text+0x4c9c4): undefined reference to `__virt_addr_valid'
    snapshot.c:(.text+0x4ca58): undefined reference to `__virt_addr_valid'
    kernel/built-in.o: In function `snapshot_write_next':
    (.text+0x4e44c): undefined reference to `__virt_addr_valid'
    kernel/built-in.o: In function `snapshot_write_next':
    (.text+0x4e890): undefined reference to `__virt_addr_valid'
    make[1]: *** [vmlinux] Error 1
    make: *** [sub-make] Error 2
    
    I suspect that __virt_addr_valid() is fine for mips 64. I moved it to
    mmap.c such that it gets compiled for mips 64 and 32.
    
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
    Cc: linux-kernel@vger.kernel.org
    Cc: linux-mips@linux-mips.org
    Patchwork: https://patchwork.linux-mips.org/patch/4842/
    Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
  8. @snitm

    dm thin: fix queue limits stacking

    snitm authored Alasdair G Kergon committed
    thin_io_hints() is blindly copying the queue limits from the thin-pool
    which can lead to incorrect limits being set.  The fix here simply
    deletes the thin_io_hints() hook which leaves the existing stacking
    infrastructure to set the limits correctly.
    
    When a thin-pool uses an MD device for the data device a thin device
    from the thin-pool must respect MD's constraints about disallowing a bio
    from spanning multiple chunks.  Otherwise we can see problems.  If the raid0
    chunksize is 1152K and thin-pool chunksize is 256K I see the following
    md/raid0 error (with extra debug tracing added to thin_endio) when
    mkfs.xfs is executed against the thin device:
    
    md/raid0:md99: make_request bug: can't convert block across chunks or bigger than 1152k 6688 127
    device-mapper: thin: bio sector=2080 err=-5 bi_size=130560 bi_rw=17 bi_vcnt=32 bi_idx=0
    
    This extra DM debugging shows that the failing bio is spanning across
    the first and second logical 1152K chunk (sector 2080 + 255 takes the
    bio beyond the first chunk's boundary of sector 2304).  So the bio
    splitting that DM is doing clearly isn't respecting the MD limits.
    
    max_hw_sectors_kb is 127 for both the thin-pool and thin device
    (queue_max_hw_sectors returns 255 so we'll excuse sysfs's lack of
    precision).  So this explains why bi_size is 130560.
    
    But the thin device's max_hw_sectors_kb should be 4 (PAGE_SIZE) given
    that it doesn't have a .merge function (for bio_add_page to consult
    indirectly via dm_merge_bvec) yet the thin-pool does sit above an MD
    device that has a compulsory merge_bvec_fn.  This scenario is exactly
    why DM must resort to sending single PAGE_SIZE bios to the underlying
    layer. Some additional context for this is available in the header for
    commit 8cbeb67 ("dm: avoid unsupported spanning of md stripe boundaries").
    
    Long story short, the reason a thin device doesn't properly get
    configured to have a max_hw_sectors_kb of 4 (PAGE_SIZE) is that
    thin_io_hints() is blindly copying the queue limits from the thin-pool
    device directly to the thin device's queue limits.
    
    Fix this by eliminating thin_io_hints.  Doing so is safe because the
    block layer's queue limits stacking already enables the upper level thin
    device to inherit the thin-pool device's discard and minimum_io_size and
    optimal_io_size limits that get set in pool_io_hints.  But avoiding the
    queue limits copy allows the thin and thin-pool limits to be different
    where it is important, namely max_hw_sectors_kb.
    
    Reported-by: Daniel Browning <db@kavod.com>
    Signed-off-by: Mike Snitzer <snitzer@redhat.com>
    Cc: stable@vger.kernel.org
    Signed-off-by: Alasdair G Kergon <agk@redhat.com>
  9. @torvalds

    Merge branch 'x86-efi-for-linus' of git://git.kernel.org/pub/scm/linu…

    torvalds authored
    …x/kernel/git/tip/tip
    
    Pull x86 EFI fixes from Peter Anvin:
     "This is a collection of fixes for the EFI support.  The controversial
      bit here is a set of patches which bumps the boot protocol version as
      part of fixing some serious problems with the EFI handover protocol,
      used when booting under EFI using a bootloader as opposed to directly
      from EFI.  These changes should also make it a lot saner to support
      cross-mode 32/64-bit EFI booting in the future.  Getting these changes
      into 3.8 means we avoid presenting an inconsistent ABI to bootloaders.
    
      Other changes are display detection and fixing efivarfs."
    
    * 'x86-efi-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      x86, efi: remove attribute check from setup_efi_pci
      x86, build: Dynamically find entry points in compressed startup code
      x86, efi: Fix PCI ROM handing in EFI boot stub, in 32-bit mode
      x86, efi: Fix 32-bit EFI handover protocol entry point
      x86, efi: Fix display detection in EFI boot stub
      x86, boot: Define the 2.12 bzImage boot protocol
      x86/boot: Fix minor fd leakage in tools/relocs.c
      x86, efi: Set runtime_version to the EFI spec revision
      x86, efi: fix 32-bit warnings in setup_efi_pci()
      efivarfs: Delete dentry from dcache in efivarfs_file_write()
      efivarfs: Never return ENOENT from firmware
      efi, x86: Pass a proper identity mapping in efi_call_phys_prelog
      efivarfs: Drop link count of the right inode
  10. @torvalds

    Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/l…

    torvalds authored
    …inux/kernel/git/tip/tip
    
    Pull x86 fixes from Peter Anvin:
     "This is a collection of miscellaneous fixes, the most important one is
      the fix for the Samsung laptop bricking issue (auto-blacklisting the
      samsung-laptop driver); the efi_enabled() changes you see below are
      prerequisites for that fix.
    
      The other issues fixed are booting on OLPC XO-1.5, an UV fix, NMI
      debugging, and requiring CAP_SYS_RAWIO for MSR references, just as
      with I/O port references."
    
    * 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
      samsung-laptop: Disable on EFI hardware
      efi: Make 'efi_enabled' a function to query EFI facilities
      smp: Fix SMP function call empty cpu mask race
      x86/msr: Add capabilities check
      x86/dma-debug: Bump PREALLOC_DMA_DEBUG_ENTRIES
      x86/olpc: Fix olpc-xo1-sci.c build errors
      arch/x86/platform/uv: Fix incorrect tlb flush all issue
      x86-64: Fix unwind annotations in recent NMI changes
      x86-32: Start out cr0 clean, disable paging before modifying cr3/4
  11. @torvalds

    Merge branch 'drm-fixes' of git://people.freedesktop.org/~airlied/linux

    torvalds authored
    Pull console lockdep checking revert from Dave Airlie.
    
    The lockdep splat this showed was interesting, but it's very very old,
    and we won't be fixing it until 3.9.  In the meantime, undo the lockdep
    annotation so that we don't generate the (known) console lockdep issue,
    and then possibly hide any potential other (unknown) lockdep problems
    that got disabled by the first one that triggered.
    
    * 'drm-fixes' of git://people.freedesktop.org/~airlied/linux:
      Revert "console: implement lockdep support for console_lock"
  12. @airlied

    Revert "console: implement lockdep support for console_lock"

    airlied authored
    This reverts commit daee779.
    
    I'll requeue this after the console locking fixes, so lockdep
    is useful again for people until fbcon is fixed.
    
    Signed-off-by: Dave Airlie <airlied@redhat.com>
Commits on Jan 30, 2013
  1. NFSv4.1: Handle NFS4ERR_DELAY when resetting the NFSv4.1 session

    Trond Myklebust authored
    NFS4ERR_DELAY is a legal reply when we call DESTROY_SESSION. It
    usually means that the server is busy handling an unfinished RPC
    request. Just sleep for a second and then retry.
    We also need to be able to handle the NFS4ERR_BACK_CHAN_BUSY return
    value. If the NFS server has outstanding callbacks, we just want to
    similarly sleep & retry.
    
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
    Cc: stable@vger.kernel.org
  2. SUNRPC: When changing the queue priority, ensure that we change the o…

    Trond Myklebust authored
    …wner
    
    This fixes a livelock in the xprt->sending queue where we end up never
    making progress on lower priority tasks because sleep_on_priority()
    keeps adding new tasks with the same owner to the head of the queue,
    and priority bumps mean that we keep resetting the queue->owner to
    whatever task is at the head of the queue.
    
    Regression introduced by commit c05eecf
    (SUNRPC: Don't allow low priority tasks to pre-empt higher priority ones).
    
    Reported-by: Andy Adamson <andros@netapp.com>
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
  3. Merge tag 'efi-for-3.8' into x86/efi

    H. Peter Anvin authored
    Various urgent EFI fixes and some warning cleanups for v3.8
    
      * EFI boot stub fix for Macbook Pro's from Maarten Lankhorst
      * Fix an oops in efivarfs from Lingzhu Xiang
      * 32-bit warning cleanups from Jan Beulich
      * Patch to Boot on >512GB RAM systems from Nathan Zimmer
      * Set efi.runtime_version correctly
      * efivarfs updates
    
    Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
  4. NFS: Don't silently fail setattr() requests on mountpoints

    Trond Myklebust authored
    Ensure that any setattr and getattr requests for junctions and/or
    mountpoints are sent to the server. Ever since commit
    0ec26fd (vfs: automount should ignore LOOKUP_FOLLOW), we have
    silently dropped any setattr requests to a server-side mountpoint.
    For referrals, we have silently dropped both getattr and setattr
    requests.
    
    This patch restores the original behaviour for setattr on mountpoints,
    and tries to do the same for referrals, provided that we have a
    filehandle...
    
    Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
    Cc: stable@vger.kernel.org
  5. @jchandra-brcm @ralfbaechle

    MIPS: Netlogic: Fix UP compilation on XLR

    jchandra-brcm authored ralfbaechle committed
    The commit 2a37b1a "MIPS: Netlogic: Move from u32 cpumask to cpumask_t"
    breaks uniprocessor compilation on XLR with:
    
    arch/mips/netlogic/xlr/setup.c: In function 'prom_init':
    arch/mips/netlogic/xlr/setup.c:196:6: error: unused variable 'i'
    
    Fix by defining 'i' only when CONFIG_SMP is defined.
    
    Signed-off-by: Jayachandran C <jchandra@broadcom.com>
    Patchwork: http://patchwork.linux-mips.org/patch/4760/
    Signed-off-by: John Crispin <blogic@openwrt.org>
    Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
  6. @ralfbaechle

    MIPS: AR71xx: Fix AR71XX_PCI_MEM_SIZE

    Gabor Juhos authored ralfbaechle committed
    The base address of the PCI memory is 0x10000000 and the base address of the
    PCI configuration space is 0x17000000 on the AR71xx SoCs.
    
    The AR71XX_PCI_MEM_SIZE is defined as 0x08000000 which is wrong because that
    overlaps with the configuration space.  This patch fixes the value of the
    AR71XX_PCI_MEM_SIZE constant, in order to avoid this resource conflicts.
    
    Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
    Patchwork: http://patchwork.linux-mips.org/patch/4873/
    Signed-off-by: John Crispin <blogic@openwrt.org>
    Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
  7. @ralfbaechle

    MIPS: AR724x: Fix AR724X_PCI_MEM_SIZE

    Gabor Juhos authored ralfbaechle committed
    The base address of the PCI memory is
    0x10000000 and the base address of the
    PCI configuration space is 0x14000000
    on the AR724x SoCs.
    
    The AR724X_PCI_MEM_SIZE is defined as
    0x08000000 which is wrong because that
    overlaps  with the configuration space.
    
    The patch fixes the value of the
    AR724X_PCI_MEM_SIZE constant, in order
    to avoid this resource conflicts.
    
    Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
    Patchwork: http://patchwork.linux-mips.org/patch/4872/
    Signed-off-by: John Crispin <blogic@openwrt.org>
    Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Something went wrong with that request. Please try again.