1. 16 Apr, 2017 1 commit
  2. 07 Apr, 2017 3 commits
  3. 06 Apr, 2017 1 commit
  4. 04 Apr, 2017 2 commits
    • Dave Gerlach's avatar
      ARM: OMAP2+: omap_device: Sync omap_device and pm_runtime after probe defer · 04abaf07
      Dave Gerlach authored
      Starting from commit 5de85b9d ("PM / runtime: Re-init runtime PM
      states at probe error and driver unbind") pm_runtime core now changes
      device runtime_status back to after RPM_SUSPENDED after a probe defer.
      Certain OMAP devices make use of "ti,no-idle-on-init" flag which causes
      omap_device_enable to be called during the BUS_NOTIFY_ADD_DEVICE event
      during probe, along with pm_runtime_set_active.
      
      This call to pm_runtime_set_active typically will prevent a call to
      pm_runtime_get in a driver probe function from re-enabling the
      omap_device. However, in the case of a probe defer that happens before
      the driver probe function is able to run, such as a missing pinctrl
      states defer, pm_runtime_reinit will set the device as RPM_SUSPENDED and
      then once driver probe is actually able to run, pm_runtime_get will see
      the device as suspended and call through to the omap_device layer,
      attempting to enable the already enabled omap_device and causing errors
      like this:
      
      omap-gpmc 50000000.gpmc: omap_device: omap_device_enable() called from
      invalid state 1
      omap-gpmc 50000000.gpmc: use pm_runtime_put_sync_suspend() in driver?
      
      We can avoid this error by making sure the pm_runtime status of a device
      matches the omap_device state before a probe attempt. By extending the
      omap_device bus notifier to act on the BUS_NOTIFY_BIND_DRIVER event we
      can check if a device is enabled in omap_device but with a pm_runtime
      status of RPM_SUSPENDED and once again mark the device as RPM_ACTIVE to
      avoid a second incorrect call to omap_device_enable.
      
      Fixes: 5de85b9d ("PM / runtime: Re-init runtime PM states at probe
      error and driver unbind")
      Tested-by: default avatarFranklin S Cooper Jr. <fcooper@ti.com>
      Signed-off-by: default avatarDave Gerlach <d-gerlach@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      04abaf07
    • Philipp Zabel's avatar
      reset: add exported __reset_control_get, return NULL if optional · 62e24c57
      Philipp Zabel authored
      Rename the internal __reset_control_get/put functions to
      __reset_control_get/put_internal and add an exported
      __reset_control_get equivalent to __of_reset_control_get
      that takes a struct device parameter.
      This avoids the confusing call to __of_reset_control_get in
      the non-DT case and fixes the devm_reset_control_get_optional
      function to return NULL if RESET_CONTROLLER is enabled but
      dev->of_node == NULL.
      
      Fixes: bb475230 ("reset: make optional functions really optional")
      Reported-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      Tested-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      Cc: Ramiro Oliveira <Ramiro.Oliveira@synopsys.com>
      Signed-off-by: default avatarPhilipp Zabel <p.zabel@pengutronix.de>
      62e24c57
  5. 30 Mar, 2017 1 commit
    • Arnd Bergmann's avatar
      ARM: orion5x: only call into phylib when available · d43e85b7
      Arnd Bergmann authored
      Board code cannot call mdiobus_register_board_info() when phylib
      or mdio_device is a loadable module:
      
      arch/arm/plat-orion/common.o: In function `orion_ge00_switch_init':
      :(.init.text+0x474): undefined reference to `mdiobus_register_board_info'
      
      I had a number of ideas for how this could be solved, but after the MDIO
      code got split out from PHYLIB it has gotten too hard, so I'm basically
      giving up, and only call the mdiobus_register_board_info() function
      if the MDIO layer is built-in to avoid the link error. This is similar
      to how we handle PHY registration on other ARM platforms.
      
      Fixes: 90eff909 ("net: phy: Allow splitting MDIO bus/device support from PHYs")
      Fixes: 648ea013 ("net: phy: Allow pre-declaration of MDIO devices")
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarGregory CLEMENT <gregory.clement@free-electrons.com>
      d43e85b7
  6. 27 Mar, 2017 2 commits
    • Tony Lindgren's avatar
      ARM: omap2+: Revert omap-smp.c changes resetting CPU1 during boot · 351b7c49
      Tony Lindgren authored
      Commit 32518852 ("ARM: OMAP4+: Reset CPU1 properly for kexec") started
      unconditionally resetting CPU1 because of a kexec boot issue I was seeing
      earlier on omap4 when doing kexec boot between two different kernel
      versions.
      
      This caused issues on some systems. We should only reset CPU1 as a last
      resort option, and try to avoid it where possible. Doing an unconditional
      CPU1 reset causes issues for example when booting a bootloader configured
      secure OS running on CPU1 as reported by Andrew F. Davis <afd@ti.com>.
      
      We can't completely remove the reset of CPU1 as it would break kexec
      booting from older kernels. But we can limit the CPU1 reset to cases
      where CPU1 is wrongly parked within the memory area used by the booting
      kernel. Then later on we can add support for parking CPU1 for kexec out
      of the SDRAM back to bootrom.
      
      So let's first fix the regression reported by Andrew by making CPU1 reset
      conditional. To do this, we need to:
      
      1. Save configured AUX_CORE_BOOT_1 for later
      
      2. Modify AUX_CORE_BOOT_0 reading code to for HS SoCs to return
         the whole register instead of the CPU mask
      
      3. Check if CPU1 is wrongly parked into the booting kernel by the
         previous kernel and reset if needed
      
      Fixes: 32518852 ("ARM: OMAP4+: Reset CPU1 properly for kexec")
      Reported-by: default avatarAndrew F. Davis <afd@ti.com>
      Cc: Andrew F. Davis <afd@ti.com>
      Cc: Keerthy <j-keerthy@ti.com>
      Cc: Russell King <rmk+kernel@armlinux.org.uk>
      Cc: Santosh Shilimkar <ssantosh@kernel.org>
      Cc: Tero Kristo <t-kristo@ti.com>
      Tested-by: default avatarKeerthy <j-keerthy@ti.com>
      Tested-by: default avatarAndrew F. Davis <afd@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      351b7c49
    • Reizer, Eyal's avatar
      ARM: dts: am335x-evmsk: adjust mmc2 param to allow suspend · 9bcf53f3
      Reizer, Eyal authored
      mmc2 used for wl12xx was missing the keep-power-in suspend
      parameter. As a result the board couldn't reach suspend state.
      Signed-off-by: default avatarEyal Reizer <eyalr@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      9bcf53f3
  7. 24 Mar, 2017 2 commits
  8. 23 Mar, 2017 3 commits
  9. 22 Mar, 2017 6 commits
  10. 21 Mar, 2017 2 commits
  11. 20 Mar, 2017 2 commits
  12. 16 Mar, 2017 1 commit
    • Jon Mason's avatar
      ARM: dts: NSP: GPIO reboot open-source · acfa28b3
      Jon Mason authored
      The libgpio code pre-sets the GPIO values for the gpio-reset in the
      device tree.  This results in the device being reset during bringup.
      To prevent this pre-setting, use the "open-source" flag in the device
      tree.
      Signed-off-by: default avatarJon Mason <jon.mason@broadcom.com>
      Fixes: b1aaf88b ("ARM: dts: NSP: Add GPIO reboot method to bcm958625hr DTS file")
      Fixes: 10baed1c ("ARM: dts: NSP: Add GPIO reboot method to bcm958625xmc DTS file")
      Fixes: 088e3148 ("ARM: dts: NSP: Add new DT file for bcm958522er")
      Fixes: e3227c12 ("ARM: dts: NSP: Add new DT file for bcm958525er")
      Fixes: 2f8bc002 ("ARM: dts: NSP: Add new DT file for bcm958622hr")
      Fixes: d454c376 ("ARM: dts: NSP: Add new DT file for bcm958623hr")
      Fixes: f27eacf2 ("ARM: dts: NSP: Add new DT file for bcm988312hr")
      Signed-off-by: default avatarFlorian Fainelli <f.fainelli@gmail.com>
      acfa28b3
  13. 14 Mar, 2017 1 commit
    • Nicolas Ferre's avatar
      ARM: at91: pm: cpu_idle: switch DDR to power-down mode · 60b89f19
      Nicolas Ferre authored
      On some DDR controllers, compatible with the sama5d3 one,
      the sequence to enter/exit/re-enter the self-refresh mode adds
      more constrains than what is currently written in the at91_idle
      driver. An actual access to the DDR chip is needed between exit
      and re-enter of this mode which is somehow difficult to implement.
      This sequence can completely hang the SoC. It is particularly
      experienced on parts which embed a L2 cache if the code run
      between IDLE calls fits in it...
      
      Moreover, as the intention is to enter and exit pretty rapidly
      from IDLE, the power-down mode is a good candidate.
      
      So now we use power-down instead of self-refresh. As we can
      simplify the code for sama5d3 compatible DDR controllers,
      we instantiate a new sama5d3_ddr_standby() function.
      Signed-off-by: default avatarNicolas Ferre <nicolas.ferre@microchip.com>
      Cc: <stable@vger.kernel.org> # v4.1+
      Fixes: 017b5522 ("ARM: at91: Add new binding for sama5d3-ddramc")
      Signed-off-by: default avatarAlexandre Belloni <alexandre.belloni@free-electrons.com>
      60b89f19
  14. 13 Mar, 2017 3 commits
    • Olof Johansson's avatar
      Merge tag 'omap-for-v4.11/fixes-rc1-v2' of... · 42d5d460
      Olof Johansson authored
      Merge tag 'omap-for-v4.11/fixes-rc1-v2' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into fixes
      
      Fixes for omaps for v4.11-rc cycle:
      
      - Fix smartreflex platform data regression where I accidentally
        removed legacy platform data still in use
      - Fix hypervisor mode for thumb2 kernel
      - Fix misplaced tpic2810 to move it to right bus
      - Enable INPUT_MOUSEDEV as a loadable module have mice working
      - Fix use of gpio-key,wakeup and use wakeup-source instead as
        this accidentally sneaked in during the merge window
      - Fix error handling for onenand to properly return error
      - Remove legacy gpmc-nand.c that's now dead code, this
        also removes dependency to the MTD tree for further driver
        changes
      - Fix device node reference count errors for omap3 and
        related to it also release device nodes after no longer
        needed
      
      * tag 'omap-for-v4.11/fixes-rc1-v2' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap:
        ARM: OMAP2+: Release device node after it is no longer needed.
        ARM: OMAP2+: Fix device node reference counts
        ARM: OMAP2+: Remove legacy gpmc-nand.c
        ARM: OMAP2+: gpmc-onenand: propagate error on initialization failure
        ARM: dts: am335x-pcm953: Fix legacy wakeup source binding
        ARM: omap2plus_defconfig: Enable INPUT_MOUSEDEV as loadable modules
        ARM: dts: am57xx-idk: tpic2810 is on I2C bus, not SPI
        ARM: OMAP5 / DRA7: Fix HYP mode boot for thumb2 build
        ARM: OMAP3: Fix smartreflex platform data regression
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      42d5d460
    • Olof Johansson's avatar
      Merge tag 'arm-soc/for-4.11/devicetree-fixes' of http://github.com/Broadcom/stblinux into fixes · f40624e8
      Olof Johansson authored
      This pull request contains Broadcom ARM-based SoC Device Tree fixes for 4.11,
      please pull the following:
      
      - Jon fixes the UART output on the Broadcom bcm953012k reference board by
        using the proper clock reference instead of hard-coding the baud rate
      
      - Jon also fixes the memory map on the bcm953012k reference board by using
        the appropriate physical RAM start address
      
      - Jon finally fixes the interrupt type for the Cortex A9 global and local
        timers found in the BCM5301X SoC (Norsthar).
      
      * tag 'arm-soc/for-4.11/devicetree-fixes' of http://github.com/Broadcom/stblinux:
        ARM: dts: BCM5301X: Correct GIC_PPI interrupt flags
        ARM: dts: BCM5301X: Fix memory start address
        ARM: dts: BCM5301X: Fix UARTs on bcm953012k
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      f40624e8
    • Linus Walleij's avatar
      ARM: dts: add the AB8500 clocks to the device tree · 9aea151f
      Linus Walleij authored
      This adds the AB8500 clocks to the device tree using the new
      bindings from the clk subsystem, making audio work again.
      
      Cc: Lee Jones <lee.jones@linaro.org>
      Cc: Ulf Hansson <ulf.hansson@linaro.org>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      9aea151f
  15. 12 Mar, 2017 5 commits
    • Linus Torvalds's avatar
      Linux 4.11-rc2 · 4495c08e
      Linus Torvalds authored
      4495c08e
    • Linus Torvalds's avatar
      Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux · 56b24d1b
      Linus Torvalds authored
      Pull s390 fixes from Martin Schwidefsky:
      
       - four patches to get the new cputime code in shape for s390
      
       - add the new statx system call
      
       - a few bug fixes
      
      * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux:
        s390: wire up statx system call
        KVM: s390: Fix guest migration for huge guests resulting in panic
        s390/ipl: always use load normal for CCW-type re-IPL
        s390/timex: micro optimization for tod_to_ns
        s390/cputime: provide archicture specific cputime_to_nsecs
        s390/cputime: reset all accounting fields on fork
        s390/cputime: remove last traces of cputime_t
        s390: fix in-kernel program checks
        s390/crypt: fix missing unlock in ctr_paes_crypt on error path
      56b24d1b
    • Linus Torvalds's avatar
      Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip · 5a45a5a8
      Linus Torvalds authored
      Pull x86 fixes from Thomas Gleixner:
      
       - a fix for the kexec/purgatory regression which was introduced in the
         merge window via an innocent sparse fix. We could have reverted that
         commit, but on deeper inspection it turned out that the whole
         machinery is neither documented nor robust. So a proper cleanup was
         done instead
      
       - the fix for the TLB flush issue which was discovered recently
      
       - a simple typo fix for a reboot quirk
      
      * 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
        x86/tlb: Fix tlb flushing when lguest clears PGE
        kexec, x86/purgatory: Unbreak it and clean it up
        x86/reboot/quirks: Fix typo in ASUS EeeBook X205TA reboot quirk
      5a45a5a8
    • Linus Torvalds's avatar
      Merge branch 'irq-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip · ecade114
      Linus Torvalds authored
      Pull irq fixes from Thomas Gleixner:
      
       - a workaround for a GIC erratum
      
       - a missing stub function for CONFIG_IRQDOMAIN=n
      
       - fixes for a couple of type inconsistencies
      
      * 'irq-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
        irqchip/crossbar: Fix incorrect type of register size
        irqchip/gicv3-its: Add workaround for QDF2400 ITS erratum 0065
        irqdomain: Add empty irq_domain_check_msi_remap
        irqchip/crossbar: Fix incorrect type of local variables
      ecade114
    • Daniel Borkmann's avatar
      x86/tlb: Fix tlb flushing when lguest clears PGE · 2c4ea6e2
      Daniel Borkmann authored
      Fengguang reported random corruptions from various locations on x86-32
      after commits d2852a22 ("arch: add ARCH_HAS_SET_MEMORY config") and
      9d876e79 ("bpf: fix unlocking of jited image when module ronx not set")
      that uses the former. While x86-32 doesn't have a JIT like x86_64, the
      bpf_prog_lock_ro() and bpf_prog_unlock_ro() got enabled due to
      ARCH_HAS_SET_MEMORY, whereas Fengguang's test kernel doesn't have module
      support built in and therefore never had the DEBUG_SET_MODULE_RONX setting
      enabled.
      
      After investigating the crashes further, it turned out that using
      set_memory_ro() and set_memory_rw() didn't have the desired effect, for
      example, setting the pages as read-only on x86-32 would still let
      probe_kernel_write() succeed without error. This behavior would manifest
      itself in situations where the vmalloc'ed buffer was accessed prior to
      set_memory_*() such as in case of bpf_prog_alloc(). In cases where it
      wasn't, the page attribute changes seemed to have taken effect, leading to
      the conclusion that a TLB invalidate didn't happen. Moreover, it turned out
      that this issue reproduced with qemu in "-cpu kvm64" mode, but not for
      "-cpu host". When the issue occurs, change_page_attr_set_clr() did trigger
      a TLB flush as expected via __flush_tlb_all() through cpa_flush_range(),
      though.
      
      There are 3 variants for issuing a TLB flush: invpcid_flush_all() (depends
      on CPU feature bits X86_FEATURE_INVPCID, X86_FEATURE_PGE), cr4 based flush
      (depends on X86_FEATURE_PGE), and cr3 based flush.  For "-cpu host" case in
      my setup, the flush used invpcid_flush_all() variant, whereas for "-cpu
      kvm64", the flush was cr4 based. Switching the kvm64 case to cr3 manually
      worked fine, and further investigating the cr4 one turned out that
      X86_CR4_PGE bit was not set in cr4 register, meaning the
      __native_flush_tlb_global_irq_disabled() wrote cr4 twice with the same
      value instead of clearing X86_CR4_PGE in the first write to trigger the
      flush.
      
      It turned out that X86_CR4_PGE was cleared from cr4 during init from
      lguest_arch_host_init() via adjust_pge(). The X86_FEATURE_PGE bit is also
      cleared from there due to concerns of using PGE in guest kernel that can
      lead to hard to trace bugs (see bff672e6 ("lguest: documentation V:
      Host") in init()). The CPU feature bits are cleared in dynamic
      boot_cpu_data, but they never propagated to __flush_tlb_all() as it uses
      static_cpu_has() instead of boot_cpu_has() for testing which variant of TLB
      flushing to use, meaning they still used the old setting of the host
      kernel.
      
      Clearing via setup_clear_cpu_cap(X86_FEATURE_PGE) so this would propagate
      to static_cpu_has() checks is too late at this point as sections have been
      patched already, so for now, it seems reasonable to switch back to
      boot_cpu_has(X86_FEATURE_PGE) as it was prior to commit c109bf95
      ("x86/cpufeature: Remove cpu_has_pge"). This lets the TLB flush trigger via
      cr3 as originally intended, properly makes the new page attributes visible
      and thus fixes the crashes seen by Fengguang.
      
      Fixes: c109bf95 ("x86/cpufeature: Remove cpu_has_pge")
      Reported-by: default avatarFengguang Wu <fengguang.wu@intel.com>
      Signed-off-by: default avatarDaniel Borkmann <daniel@iogearbox.net>
      Cc: bp@suse.de
      Cc: Kees Cook <keescook@chromium.org>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: netdev@vger.kernel.org
      Cc: Rusty Russell <rusty@rustcorp.com.au>
      Cc: Alexei Starovoitov <ast@kernel.org>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: lkp@01.org
      Cc: Laura Abbott <labbott@redhat.com>
      Cc: stable@vger.kernel.org
      Link: http://lkml.kernrl.org/r/20170301125426.l4nf65rx4wahohyl@wfg-t540p.sh.intel.com
      Link: http://lkml.kernel.org/r/25c41ad9eca164be4db9ad84f768965b7eb19d9e.1489191673.git.daniel@iogearbox.netSigned-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      2c4ea6e2
  16. 11 Mar, 2017 5 commits
    • Linus Torvalds's avatar
      Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm · 106e4da6
      Linus Torvalds authored
      Pull KVM fixes from Radim Krčmář:
       "ARM updates from Marc Zyngier:
         - vgic updates:
           - Honour disabling the ITS
           - Don't deadlock when deactivating own interrupts via MMIO
           - Correctly expose the lact of IRQ/FIQ bypass on GICv3
      
         - I/O virtualization:
           - Make KVM_CAP_NR_MEMSLOTS big enough for large guests with many
             PCIe devices
      
         - General bug fixes:
           - Gracefully handle exception generated with syndroms that the host
             doesn't understand
           - Properly invalidate TLBs on VHE systems
      
        x86:
         - improvements in emulation of VMCLEAR, VMX MSR bitmaps, and VCPU
           reset
      
      * tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm:
        KVM: nVMX: do not warn when MSR bitmap address is not backed
        KVM: arm64: Increase number of user memslots to 512
        KVM: arm/arm64: Remove KVM_PRIVATE_MEM_SLOTS definition that are unused
        KVM: arm/arm64: Enable KVM_CAP_NR_MEMSLOTS on arm/arm64
        KVM: Add documentation for KVM_CAP_NR_MEMSLOTS
        KVM: arm/arm64: VGIC: Fix command handling while ITS being disabled
        arm64: KVM: Survive unknown traps from guests
        arm: KVM: Survive unknown traps from guests
        KVM: arm/arm64: Let vcpu thread modify its own active state
        KVM: nVMX: reset nested_run_pending if the vCPU is going to be reset
        kvm: nVMX: VMCLEAR should not cause the vCPU to shut down
        KVM: arm/arm64: vgic-v3: Don't pretend to support IRQ/FIQ bypass
        arm64: KVM: VHE: Clear HCR_TGE when invalidating guest TLBs
      106e4da6
    • Linus Torvalds's avatar
      Merge tag 'extable-fix' of git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux · 4b050f22
      Linus Torvalds authored
      Pull extable.h fix from Paul Gortmaker:
       "Fixup for arch/score after extable.h introduction.
      
        It seems that Guenter is the only one on the planet doing builds for
        arch/score -- we don't have compile coverage for it in linux-next or
        in the kbuild-bot either. Guenter couldn't even recall where he got
        his toolchain, but was kind enough to share it with me so I could
        validate this change and also add arch/score to my build coverage.
      
        I sat on this a bit in case there was any other fallout in other arch
        dirs, but since this still seems to be the only one, I might as well
        send it on its way"
      
      * tag 'extable-fix' of git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux:
        score: Fix implicit includes now failing build after extable change
      4b050f22
    • Linus Torvalds's avatar
      Merge tag 'random_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random · 84c37c16
      Linus Torvalds authored
      Pull random updates from Ted Ts'o:
       "Change get_random_{int,log} to use the CRNG used by /dev/urandom and
        getrandom(2). It's faster and arguably more secure than cut-down MD5
        that we had been using.
      
        Also do some code cleanup"
      
      * tag 'random_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random:
        random: move random_min_urandom_seed into CONFIG_SYSCTL ifdef block
        random: convert get_random_int/long into get_random_u32/u64
        random: use chacha20 for get_random_int/long
        random: fix comment for unused random_min_urandom_seed
        random: remove variable limit
        random: remove stale urandom_init_wait
        random: remove stale maybe_reseed_primary_crng
      84c37c16
    • Guenter Roeck's avatar
      score: Fix implicit includes now failing build after extable change · 0acf6119
      Guenter Roeck authored
      After changing from module.h to extable.h, score builds fail with:
      
        arch/score/kernel/traps.c: In function 'do_ri':
        arch/score/kernel/traps.c:248:4: error: implicit declaration of function 'user_disable_single_step'
        arch/score/mm/extable.c: In function 'fixup_exception':
        arch/score/mm/extable.c:32:38: error: dereferencing pointer to incomplete type
        arch/score/mm/extable.c:34:24: error: dereferencing pointer to incomplete type
      
      because extable.h doesn't drag in the same amount of headers as the
      module.h did.  Add in the headers which were implicitly expected.
      
      Fixes: 90858794 ("module.h: remove extable.h include now users have migrated")
      Signed-off-by: default avatarGuenter Roeck <linux@roeck-us.net>
      [PG: tweak commit log; refresh for sched header refactoring.]
      Signed-off-by: default avatarPaul Gortmaker <paul.gortmaker@windriver.com>
      0acf6119
    • Linus Torvalds's avatar
      Merge tag 'tty-4.11-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty · 434fd635
      Linus Torvalds authored
      Pull tty/serial fixes frpm Greg KH:
       "Here are two bugfixes for tty stuff for 4.11-rc2.
      
        One of them resolves the pretty bad bug in the n_hdlc code that
        Alexander Popov found and fixed and has been reported everywhere. The
        other just fixes a samsung serial driver issue when DMA fails on some
        systems.
      
        Both have been in linux-next with no reported issues"
      
      * tag 'tty-4.11-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty:
        serial: samsung: Continue to work if DMA request fails
        tty: n_hdlc: get rid of racy n_hdlc.tbuf
      434fd635