Skip to content
Permalink
Branch: odroidxu4-4.9.y
Commits on Nov 9, 2017
  1. Merge pull request #323 from Dmole/odroid_config

    mdrjr committed Nov 9, 2017
    apcups support
  2. Merge tag 'v4.9.61' of git://git.kernel.org/pub/scm/linux/kernel/git/…

    mdrjr committed Nov 9, 2017
    …stable/linux-stable into odroidxu4-4.9.y
    
    This is the 4.9.61 stable release
  3. MFC Fix

    mdrjr committed Nov 9, 2017
    Squashed the following commits.
    
    From f5f691c Mon Sep 17 00:00:00 2001
    From: Thierry Escande <thierry.escande@collabora.com>
    Date: Wed, 26 Oct 2016 10:52:05 +0200
    Subject: [PATCH 1/4] videobuf2-dc: Move vb2_dc_get_base_sgt() above mmap
     callbacks
    
    This patch moves vb2_dc_get_base_sgt() function above mmap buffers
    callbacks, particularly vb2_dc_alloc() and vb2_dc_mmap() from where it
    will be called for cacheable MMAP support introduced in the next patch.
    
    Signed-off-by: Thierry Escande <thierry.escande@collabora.com>
    Signed-off-by: memeka <mihailescu2m@gmail.com>
    
    From ba49ab8 Mon Sep 17 00:00:00 2001
    From: Heng-Ruey Hsu <henryhsu@chromium.org>
    Date: Wed, 26 Oct 2016 10:52:06 +0200
    Subject: [PATCH 2/4] videobuf2-dc: Support cacheable MMAP
    
    DMA allocations for MMAP type are uncached by default. But for
    some cases, CPU has to access the buffers. ie: memcpy for format
    converter. Supporting cacheable MMAP improves huge performance.
    
    This patch enables cacheable memory for DMA coherent allocator in mmap
    buffer allocation if non-consistent DMA attribute is set and kernel
    mapping is present. Even if userspace doesn't mmap the buffer, sync
    still should be happening if kernel mapping is present.
    If not done in allocation, it is enabled when memory is mapped from
    userspace (if non-consistent DMA attribute is set).
    
    Signed-off-by: Heng-Ruey Hsu <henryhsu@chromium.org>
    Tested-by: Heng-ruey Hsu <henryhsu@chromium.org>
    Reviewed-by: Tomasz Figa <tfiga@chromium.org>
    Signed-off-by: Thierry Escande <thierry.escande@collabora.com>
    Signed-off-by: memeka <mihailescu2m@gmail.com>
    
    From 6ac779f Mon Sep 17 00:00:00 2001
    From: Marek Szyprowski <m.szyprowski@samsung.com>
    Date: Wed, 15 Feb 2017 14:08:49 +0100
    Subject: [PATCH 3/4] ARM: dma-mapping: add support for non-consistent dma_mmap
    
    Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
    Signed-off-by: memeka <mihailescu2m@gmail.com>
    
    From c7958c4 Mon Sep 17 00:00:00 2001
    From: memeka <mihailescu2m@gmail.com>
    Date: Mon, 30 Oct 2017 09:31:09 +1030
    Subject: [PATCH 4/4] media: s5p-mfc: use cacheable DMA buffers to improve
     performance
    
    Signed-off-by: memeka <mihailescu2m@gmail.com>
Commits on Nov 8, 2017
  1. Linux 4.9.61

    gregkh committed Nov 8, 2017
  2. ARM: dts: mvebu: pl310-cache disable double-linefill

    yanmarkman authored and gregkh committed Oct 15, 2016
    commit cda80a8 upstream.
    
    Under heavy system stress mvebu SoC using Cortex A9 sporadically
    encountered instability issues.
    
    The "double linefill" feature of L2 cache was identified as causing
    dependency between read and write which lead to the deadlock.
    
    Especially, it was the cause of deadlock seen under heavy PCIe traffic,
    as this dependency violates PCIE overtaking rule.
    
    Fixes: c8f5a87 ("ARM: mvebu: use DT properties to fine-tune the L2 configuration")
    Signed-off-by: Yan Markman <ymarkman@marvell.com>
    Signed-off-by: Igal Liberman <igall@marvell.com>
    Signed-off-by: Nadav Haklai <nadavh@marvell.com>
    [gregory.clement@free-electrons.com: reformulate commit log, add Armada
    375 and add Fixes tag]
    Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  3. staging: r8712u: Fix Sparse warning in rtl871x_xmit.c

    lwfinger authored and gregkh committed Feb 11, 2017
    [ Upstream commit 07222e5 ]
    
    Sparse reports the following:
      CHECK   drivers/staging/rtl8712/rtl871x_xmit.c
    drivers/staging/rtl8712/rtl871x_xmit.c:350:44: warning: restricted __le32 degrades to integer
    drivers/staging/rtl8712/rtl871x_xmit.c:491:23: warning: incorrect type in initializer (different base types)
    drivers/staging/rtl8712/rtl871x_xmit.c:491:23:    expected unsigned short [usertype] *fctrl
    drivers/staging/rtl8712/rtl871x_xmit.c:491:23:    got restricted __le16 *<noident>
    drivers/staging/rtl8712/rtl871x_xmit.c:580:36: warning: incorrect type in assignment (different base types)
    drivers/staging/rtl8712/rtl871x_xmit.c:580:36:    expected unsigned short [unsigned] [short] [usertype] <noident>
    drivers/staging/rtl8712/rtl871x_xmit.c:580:36:    got restricted __be16 [usertype] <noident>
    
    Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  4. xen: don't print error message in case of missing Xenstore entry

    jgross1 authored and gregkh committed May 30, 2017
    [ Upstream commit 4e93b64 ]
    
    When registering for the Xenstore watch of the node control/sysrq the
    handler will be called at once. Don't issue an error message if the
    Xenstore node isn't there, as it will be created only when an event
    is being triggered.
    
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
    Signed-off-by: Juergen Gross <jgross@suse.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  5. powerpc/64: Don't try to use radix MMU under a hypervisor

    paulusmack authored and gregkh committed Jan 30, 2017
    [ Upstream commit 18569c1 ]
    
    Currently, if the kernel is running on a POWER9 processor under a
    hypervisor, it will try to use the radix MMU even though it doesn't have
    the necessary code to use radix under a hypervisor (it doesn't negotiate
    use of radix, and it doesn't do the H_REGISTER_PROC_TBL hcall). The
    result is that the guest kernel will crash when it tries to turn on the
    MMU.
    
    This fixes it by looking for the /chosen/ibm,architecture-vec-5
    property, and if it exists, clears the radix MMU feature bit, before we
    decide whether to initialize for radix or HPT. This property is created
    by the hypervisor as a result of the guest calling the
    ibm,client-architecture-support method to indicate its capabilities, so
    it will indicate whether the hypervisor agreed to us using radix.
    
    Systems without a hypervisor may have this property also (for example,
    skiboot creates it), so we check the HV bit in the MSR to see whether we
    are running as a guest or not. If we are in hypervisor mode, then we can
    do whatever we like including using the radix MMU.
    
    The reason for using this property is that in future, when we have
    support for using radix under a hypervisor, we will need to check this
    property to see whether the hypervisor agreed to us using radix.
    
    Fixes: 2bfd65e ("powerpc/mm/radix: Add radix callbacks for early init routines")
    Cc: stable@vger.kernel.org # v4.7+
    Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
    Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  6. PCI: Avoid possible deadlock on pci_lock and p->pi_lock

    bjorn-helgaas authored and gregkh committed Oct 7, 2017
    [ Upstream commit cdcb33f ]
    
    pci_lock is an IRQ-safe spinlock that protects all accesses to PCI
    configuration space (see PCI_OP_READ() and PCI_OP_WRITE() in pci/access.c).
    
    The pci_cfg_access_unlock() path acquires pci_lock, then p->pi_lock (inside
    wake_up_all()).  According to lockdep, there is a possible path involving
    snbep_uncore_pci_read_counter() that could acquire them in the reverse
    order: acquiring p->pi_lock, then pci_lock, which could result in a
    deadlock.  Lockdep details are in the bugzilla below.
    
    Avoid the possible deadlock by dropping pci_lock before waking up any
    config access waiters.
    
    Link: https://bugzilla.kernel.org/show_bug.cgi?id=192901
    Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  7. drm/exynos: g2d: prevent integer overflow in

    Joonyoung Shim authored and gregkh committed Oct 7, 2017
    [ Upstream commit e41456b ]
    
    The size computations done in the ioctl function use an integer.
    If userspace submits a request with req->cmd_nr or req->cmd_buf_nr
    set to INT_MAX, the integer computations overflow later, leading
    to potential (kernel) memory corruption.
    
    Prevent this issue by enforcing a limit on the number of submitted
    commands, so that we have enough headroom later for the size
    computations.
    
    Note that this change has no impact on the currently available
    users in userspace, like e.g. libdrm/exynos.
    
    While at it, also make a comment about the size computation more
    detailed.
    
    Signed-off-by: Joonyoung Shim <jy0922.shim@samsung.com>
    Signed-off-by: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
    Signed-off-by: Inki Dae <inki.dae@samsung.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  8. bt8xx: fix memory leak

    sudipm-mukherjee authored and gregkh committed Oct 7, 2017
    [ Upstream commit 6792eb0 ]
    
    If dvb_attach() fails then we were just printing an error message and
    exiting but the memory allocated to state was not released.
    
    Signed-off-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
    Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  9. s390/crypto: Extend key length check for AES-XTS in fips mode.

    Harald Freudenberger authored and gregkh committed Oct 7, 2017
    [ Upstream commit a4f2779 ]
    
    In fips mode only xts keys with 128 bit or 125 bit are allowed.
    This fix extends the xts_aes_set_key function to check for these
    valid key lengths in fips mode.
    
    Signed-off-by: Harald Freudenberger <freude@linux.vnet.ibm.com>
    Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  10. s390/prng: Adjust generation of entropy to produce real 256 bits.

    Harald Freudenberger authored and gregkh committed Oct 7, 2017
    [ Upstream commit d34b1ac ]
    
    The generate_entropy function used a sha256 for compacting
    together 256 bits of entropy into 32 bytes hash. However, it
    is questionable if a sha256 can really be used here, as
    potential collisions may reduce the max entropy fitting into
    a 32 byte hash value. So this batch introduces the use of
    sha512 instead and the required buffer adjustments for the
    calling functions.
    
    Further more the working buffer for the generate_entropy
    function has been widened from one page to two pages. So now
    1024 stckf invocations are used to gather 256 bits of
    entropy. This has been done to be on the save side if the
    jitters of stckf values isn't as good as supposed.
    
    Signed-off-by: Harald Freudenberger <freude@linux.vnet.ibm.com>
    Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  11. s390/dasd: check for device error pointer within state change interrupts

    stefan-haberland authored and gregkh committed Oct 7, 2017
    [ Upstream commit 2202134 ]
    
    Check if the device pointer is valid. Just a sanity check since we already
    are in the int handler of the device.
    
    Signed-off-by: Stefan Haberland <sth@linux.vnet.ibm.com>
    Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  12. mei: return error on notification request to a disconnected client

    ausyskin authored and gregkh committed Oct 7, 2017
    [ Upstream commit 7c47d2c ]
    
    Request for a notification from a disconnected client will be ignored
    silently by the FW but the caller should know that the operation hasn't
    succeeded.
    
    Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
    Signed-off-by: Tomas Winkler <tomas.winkler@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  13. exynos4-is: fimc-is: Unmap region obtained by of_iomap()

    ArvindYadavCs authored and gregkh committed Oct 7, 2017
    [ Upstream commit 4742575 ]
    
    Free memory mapping, if fimc_is_probe is not successful.
    
    Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
    Signed-off-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  14. ASoC: Intel: boards: remove .pm_ops in all Atom/DPCM machine drivers

    plbossart authored and gregkh committed Oct 7, 2017
    [ Upstream commit 3639ac1 ]
    
    This patch corrects an omission in bytcr_rt5640 and bytcr_rt5651.
    All existing machine drivers shall not use .pm_ops to avoid a double
    suspend, as initially implemented by 3f2dcbe
    ("ASoC: Intel: Remove soc pm handling to allow platform driver handle it").
    
    Reported-by: Shrirang Bagul <shrirang.bagul@canonical.com>
    Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
    Signed-off-by: Mark Brown <broonie@kernel.org>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  15. vfs: open() with O_CREAT should not create inodes with unknown ids

    Seth Forshee authored and gregkh committed Oct 7, 2017
    [ Upstream commit 1328c72 ]
    
    may_create() rejects creation of inodes with ids which lack a
    mapping into s_user_ns. However for O_CREAT may_o_create() is
    is used instead. Add a similar check there.
    
    Fixes: 036d523 ("vfs: Don't create inodes with a uid or gid unknown to the vfs")
    Signed-off-by: Seth Forshee <seth.forshee@canonical.com>
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  16. brcmfmac: check brcmf_bus_get_memdump result for error

    Rafał Miłecki authored and gregkh committed Oct 7, 2017
    [ Upstream commit f4737a6 ]
    
    This method may be unsupported (see: USB bus) or may just fail (see:
    SDIO bus).
    While at it rework logic in brcmf_sdio_bus_get_memdump function to avoid
    too many conditional code nesting levels.
    
    Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
    Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>
    Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  17. staging: lustre: lmv: Error not handled for lmv_find_target

    Ulka Vaze authored and gregkh committed Oct 7, 2017
    [ Upstream commit 30af99d ]
    
    This issue is found by smatch; has been reported as-
    Unchecked usage of potential ERR_PTR result in lmv_hsm_req_count
    and lmv_hsm_req_build. Added ERR_PTR in both functions and also
    return value check added.
    
    Signed-off-by: Ulka Vaze <ulka.vaze@yahoo.in>
    Signed-off-by: Aditya Pandit <panditadityashreesh@yahoo.com>
    Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-6523
    Reviewed-on: http://review.whamcloud.com/14918
    Reviewed-by: Dmitry Eremin <dmitry.eremin@intel.com>
    Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
    Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
    Signed-off-by: James Simmons <jsimmons@infradead.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  18. staging: lustre: ptlrpc: skip lock if export failed

    Alexander Boyko authored and gregkh committed Oct 7, 2017
    [ Upstream commit 4c43c27 ]
    
    This patch resolves IO vs eviction race.
    After eviction failed export stayed at stale list,
    a client had IO processing and reconnected during it.
    A client sent brw rpc with last lock cookie and new connection.
    The lock with failed export was found and assert was happened.
     (ost_handler.c:1812:ost_prolong_lock_one())
      ASSERTION( lock->l_export == opd->opd_exp ) failed:
    
     1. Skip the lock at ldlm_handle2lock if lock export failed.
     2. Validation of lock for IO was added at hpreq_check(). The lock
        searching is based on granted interval tree. If server doesn`t
        have a valid lock, it reply to client with ESTALE.
    
    Signed-off-by: Alexander Boyko <alexander.boyko@seagate.com>
    Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-7702
    Seagate-bug-id: MRP-2787
    Reviewed-on: http://review.whamcloud.com/18120
    Reviewed-by: Fan Yong <fan.yong@intel.com>
    Reviewed-by: Vitaly Fertman <vitaly.fertman@seagate.com>
    Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
    Signed-off-by: James Simmons <jsimmons@infradead.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  19. staging: lustre: hsm: stack overrun in hai_dump_data_field

    fzago-cray authored and gregkh committed Oct 7, 2017
    [ Upstream commit 22aadb9 ]
    
    The function hai_dump_data_field will do a stack buffer
    overrun when cat'ing /sys/fs/lustre/.../hsm/actions if an action has
    some data in it.
    
    hai_dump_data_field uses snprintf. But there is no check for
    truncation, and the value returned by snprintf is used as-is.  The
    coordinator code calls hai_dump_data_field with 12 bytes in the
    buffer. The 6th byte of data is printed incompletely to make room for
    the terminating NUL. However snprintf still returns 2, so when
    hai_dump_data_field writes the final NUL, it does it outside the
    reserved buffer, in the 13th byte of the buffer. This stack buffer
    overrun hangs my VM.
    
    Fix by checking that there is enough room for the next 2 characters
    plus the NUL terminator. Don't print half bytes. Change the format to
    02X instead of .2X, which makes more sense.
    
    Signed-off-by: frank zago <fzago@cray.com>
    Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8171
    Reviewed-on: http://review.whamcloud.com/20338
    Reviewed-by: John L. Hammond <john.hammond@intel.com>
    Reviewed-by: Jean-Baptiste Riaux <riaux.jb@intel.com>
    Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
    Signed-off-by: James Simmons <jsimmons@infradead.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  20. staging: lustre: llite: don't invoke direct_IO for the EOF case

    Yang Sheng authored and gregkh committed Oct 7, 2017
    [ Upstream commit 7775977 ]
    
    The function generic_file_read_iter() does not check EOF
    before invoke direct_IO callback. So we have to check it
    ourselves.
    
    Signed-off-by: Yang Sheng <yang.sheng@intel.com>
    Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-8969
    Reviewed-on: https://review.whamcloud.com/24552
    Reviewed-by: Bob Glossman <bob.glossman@intel.com>
    Reviewed-by: Bobi Jam <bobijam@hotmail.com>
    Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
    Signed-off-by: James Simmons <jsimmons@infradead.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  21. platform/x86: intel_mid_thermal: Fix module autoload

    martinezjavier authored and gregkh committed Oct 7, 2017
    [ Upstream commit a93151a ]
    
    If the driver is built as a module, autoload won't work because the module
    alias information is not filled. So user-space can't match the registered
    device with the corresponding module.
    
    Export the module alias information using the MODULE_DEVICE_TABLE() macro.
    
    Before this patch:
    
    $ modinfo drivers/platform/x86/intel_mid_thermal.ko | grep alias
    $
    
    After this patch:
    
    $ modinfo drivers/platform/x86/intel_mid_thermal.ko | grep alias
    alias:          platform:msic_thermal
    
    Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
    Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  22. scsi: aacraid: Process Error for response I/O

    Raghava Aditya Renukunta authored and gregkh committed Oct 7, 2017
    [ Upstream commit 4ec57fb ]
    
    Make sure that the driver processes error conditions even in the fast
    response path for response from the adapter.
    
    Signed-off-by: Raghava Aditya Renukunta <RaghavaAditya.Renukunta@microsemi.com>
    Signed-off-by: Dave Carroll <David.Carroll@microsemi.com>
    Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
    Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  23. xen/manage: correct return value check on xenbus_scanf()

    jbeulich authored and gregkh committed Oct 7, 2017
    [ Upstream commit 4fed1b1 ]
    
    A negative return value indicates an error; in fact the function at
    present won't ever return zero.
    
    Signed-off-by: Jan Beulich <jbeulich@suse.com>
    Reviewed-by: Juergen Gross <jgross@suse.com>
    Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  24. gpio: mcp23s08: Select REGMAP/REGMAP_I2C to fix build error

    AxelLin authored and gregkh committed Oct 7, 2017
    [ Upstream commit e8e1a5b ]
    
    This driver now using devm_regmap_init/devm_regmap_init_i2c, so it needs
    to select REGMAP/REGMAP_I2C accordingly.
    
    Fixes: ("3d84fdb3f0b5 gpio: mcp23s08: use regmap")
    Signed-off-by: Axel Lin <axel.lin@ingics.com>
    Acked-By: Sebastian Reichel <sre@kernel.org>
    Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  25. mtd: nand: sunxi: Fix the non-polling case in sunxi_nfc_wait_events()

    Boris Brezillon authored and gregkh committed Oct 7, 2017
    [ Upstream commit 19649e2 ]
    
    wait_for_completion_timeout() returns 0 if a timeout occurred, 1
    otherwise. Fix the sunxi_nfc_wait_events() accordingly.
    
    Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  26. clk: sunxi-ng: Check kzalloc() for errors and cleanup error path

    bebarino authored and gregkh committed Oct 7, 2017
    [ Upstream commit 5d806f9 ]
    
    This kzalloc() could fail. Let's bail out with -ENOMEM here
    instead of NULL dereferencing. That silences static checkers. We
    should also cleanup on the error path even though this function
    returning an error probably means the system won't boot.
    
    Cc: Chen-Yu Tsai <wens@csie.org>
    Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
    Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  27. ath10k: fix reading sram contents for QCA4019

    Ashok Raj Nagarajan authored and gregkh committed Oct 7, 2017
    [ Upstream commit 7f62259 ]
    
    With QCA4019 platform, SRAM address can be accessed directly from host but
    currently, we are assuming sram addresses cannot be accessed directly and
    hence we convert the addresses.
    
    While there, clean up growing hw checks during conversion of target CPU
    address to CE address. Now we have function pointer pertaining to different
    chips.
    
    Signed-off-by: Ashok Raj Nagarajan <arnagara@qti.qualcomm.com>
    Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  28. cx231xx: Fix I2C on Internal Master 3 Bus

    Oleh-Kravchenko authored and gregkh committed Oct 7, 2017
    [ Upstream commit 6c5da80 ]
    
    Internal Master 3 Bus can send and receive only 4 bytes per time.
    
    Signed-off-by: Oleh Kravchenko <oleg@kaa.org.ua>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  29. net: phy: dp83867: Recover from "port mirroring" N/A MODE4

    Lukasz Majewski authored and gregkh committed Oct 7, 2017
    [ Upstream commit ac6e058 ]
    
    The DP83867 when not properly bootstrapped - especially with LED_0 pin -
    can enter N/A MODE4 for "port mirroring" feature.
    
    To provide normal operation of the PHY, one needs not only to explicitly
    disable the port mirroring feature, but as well stop some IC internal
    testing (which disables RGMII communication).
    
    To do that the STRAP_STS1 (0x006E) register must be read and RESERVED bit
    11 examined. When it is set, the another RESERVED bit (11) at PHYCR
    (0x0010) register must be clear to disable testing mode and enable RGMII
    communication.
    
    Thorough explanation of the problem can be found at following e2e thread:
    "DP83867IR: Problem with RESERVED bits in PHY Control Register (PHYCR) -
    Linux driver"
    
    https://e2e.ti.com/support/interface/ethernet/f/903/p/571313/2096954#2096954
    
    Signed-off-by: Lukasz Majewski <lukma@denx.de>
    Reviewed-by: Andrew Lunn <andrew@lunn.ch>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  30. clocksource/drivers/arm_arch_timer: Add dt binding for hisilicon-1610…

    dingtianhong authored and gregkh committed Oct 7, 2017
    …10101 erratum
    
    [ Upstream commit 729e552 ]
    
    This erratum describes a bug in logic outside the core, so MIDR can't be
    used to identify its presence, and reading an SoC-specific revision
    register from common arch timer code would be awkward.  So, describe it
    in the device tree.
    
    Signed-off-by: Ding Tianhong <dingtianhong@huawei.com>
    Acked-by: Rob Herring <robh@kernel.org>
    Signed-off-by: Mark Rutland <mark.rutland@arm.com>
    Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  31. drm/fsl-dcu: check for clk_prepare_enable() error

    Fabio Estevam authored and gregkh committed Oct 7, 2017
    [ Upstream commit ef15d36 ]
    
    clk_prepare_enable() may fail, so we should better check its return
    value.
    
    Also place the of_node_put() function right after clk_prepare_enable(),
    in order to avoid calling of_node_put() twice in case clk_prepare_enable()
    fails.
    
    Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
    Signed-off-by: Stefan Agner <stefan@agner.ch>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  32. iwlwifi: mvm: use the PROBE_RESP_QUEUE to send deauth to unknown station

    egrumbach authored and gregkh committed Oct 7, 2017
    [ Upstream commit d45cb20 ]
    
    When we send a deauth to a station we don't know about, we
    need to use the PROBE_RESP queue. This can happen when we
    send a deauth to a station that is not associated to us.
    
    Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
    Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
    Signed-off-by: Sasha Levin <alexander.levin@verizon.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Older
You can’t perform that action at this time.