1. 29 Aug, 2019 3 commits
  2. 15 Aug, 2019 2 commits
    • Arnd Bergmann's avatar
      Merge tag 'amlogic-fixes' of... · 305cd70e
      Arnd Bergmann authored
      Merge tag 'amlogic-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic into arm/fixes
      arm64: dts: Amlogic fixes for v5.3-rc
      - a few small DT fixes for g12a/g12b platforms
      * tag 'amlogic-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic:
        arm64: dts: amlogic: odroid-n2: keep SD card regulator always on
        arm64: dts: meson-g12a-sei510: enable IR controller
        arm64: dts: meson-g12a: add missing dwc2 phy-names
    • Arnd Bergmann's avatar
      Merge tag 'omap-for-v5.3/fixes-rc4' of... · c372740c
      Arnd Bergmann authored
      Merge tag 'omap-for-v5.3/fixes-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap into arm/fixes
      Fixes for omap variants for v5.3-rc cycle
      We have another fix to disable voltage switching for am57xx SDIO as
      the bootrom cannot handle all the voltages after a reset that thought
      I had already sent a pull request for earlier but forgot. And we also
      update dra74x iodelay configuration for mmc3 to use the recommended
      Then I noticed we had introduced few new boot warnings with the various
      recent ti-sysc changes and wanted to fix those. I also noticed we still
      have too many warnings to be able to spot the real ones easily and fixed
      up few of those. Sure some of the warnings have been around for a long
      time and few of the fixes could have waited for the merge window, but
      having more usable dmesg log level output is a valuable.
      Other fixes are IO size correction for am335x UARTs that cause issues
      for at least FreeBSD using the same device tree file that checks that
      the child IO range is not larger than the parent has.
      For omap1 ams-delta keyboard we need to fix a irq ack that broke with
      all the recent gpio changes.
      And there are also few static checker warning fixes for recent am335x
      PM changes and ti-sysc driver and one switch fall-though update.
      * tag 'omap-for-v5.3/fixes-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap:
        soc: ti: pm33xx: Make two symbols static
        soc: ti: pm33xx: Fix static checker warnings
        ARM: OMAP: dma: Mark expected switch fall-throughs
        ARM: dts: Fix incomplete dts data for am3 and am4 mmc
        bus: ti-sysc: Simplify cleanup upon failures in sysc_probe()
        ARM: OMAP1: ams-delta-fiq: Fix missing irq_ack
        ARM: dts: dra74x: Fix iodelay configuration for mmc3
        ARM: dts: am335x: Fix UARTs length
        ARM: OMAP2+: Fix omap4 errata warning on other SoCs
        ARM: dts: Fix incorrect dcan register mapping for am3, am4 and dra7
        ARM: dts: Fix flags for gpio7
        bus: ti-sysc: Fix using configured sysc mask value
        bus: ti-sysc: Fix handling of forced idle
        ARM: OMAP2+: Fix missing SYSC_HAS_RESET_STATUS for dra7 epwmss
        ARM: dts: am57xx: Disable voltage switching for SD card
      Link: https://lore.kernel.org/r/pull-1565844391-332885@atomide.comSigned-off-by: default avatarArnd Bergmann <arnd@arndb.de>
  3. 13 Aug, 2019 17 commits
    • YueHaibing's avatar
      soc: ti: pm33xx: Make two symbols static · 4a65bbb9
      YueHaibing authored
      Fix sparse warnings:
      drivers/soc/ti/pm33xx.c:144:27: warning: symbol 'rtc_wake_src' was not declared. Should it be static?
      drivers/soc/ti/pm33xx.c:160:5: warning: symbol 'am33xx_rtc_only_idle' was not declared. Should it be static?
      Signed-off-by: default avatarYueHaibing <yuehaibing@huawei.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
    • Arnd Bergmann's avatar
      Merge tag 'imx-fixes-5.3-2' of... · ebc52623
      Arnd Bergmann authored
      Merge tag 'imx-fixes-5.3-2' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into arm/fixes
      i.MX fixes for 5.3, round 2:
       - A fix on vf610-bk4 board qspi device description to get SPI-NOR
         memory recognized correctly.
      * tag 'imx-fixes-5.3-2' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux:
        ARM: dts: vf610-bk4: Fix qspi node description
      Link: https://lore.kernel.org/r/20190812160020.GA12364@X250Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
    • Keerthy's avatar
      soc: ti: pm33xx: Fix static checker warnings · d8e0cecb
      Keerthy authored
      The patch fixes a bunch of static checker warnings.
      Reported-by: default avatarDan Carpenter <dan.carpenter@oracle.com>
      Signed-off-by: default avatarKeerthy <j-keerthy@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
    • Gustavo A. R. Silva's avatar
      ARM: OMAP: dma: Mark expected switch fall-throughs · 0c0d1ec2
      Gustavo A. R. Silva authored
      Mark switch cases where we are expecting to fall through.
      This patch fixes the following warnings:
      arch/arm/plat-omap/dma.c: In function 'omap_set_dma_src_burst_mode':
      arch/arm/plat-omap/dma.c:384:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
         if (dma_omap2plus()) {
      arch/arm/plat-omap/dma.c:393:2: note: here
        case OMAP_DMA_DATA_BURST_16:
      arch/arm/plat-omap/dma.c:394:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
         if (dma_omap2plus()) {
      arch/arm/plat-omap/dma.c:402:2: note: here
      arch/arm/plat-omap/dma.c: In function 'omap_set_dma_dest_burst_mode':
      arch/arm/plat-omap/dma.c:473:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
         if (dma_omap2plus()) {
      arch/arm/plat-omap/dma.c:481:2: note: here
      Notice that, in this particular case, the code comment is
      modified in accordance with what GCC is expecting to find.
      Reported-by: default avatarStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: default avatarGustavo A. R. Silva <gustavo@embeddedor.com>
      Reviewed-by: default avatarKees Cook <keescook@chromium.org>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
    • Tony Lindgren's avatar
      Merge branch 'ti-sysc-fixes' into fixes · 50e4b5ca
      Tony Lindgren authored
    • Tony Lindgren's avatar
      ARM: dts: Fix incomplete dts data for am3 and am4 mmc · 5b63fb90
      Tony Lindgren authored
      Commit 4e27f752 ("ARM: OMAP2+: Drop mmc platform data for am330x and
      am43xx") dropped legacy mmc platform data for am3 and am4, but missed the
      fact that we never updated the dts files for mmc3 that is directly on l3
      interconnect instead of l4 interconnect. This leads to a situation with
      no legacy platform data and incomplete dts data.
      Let's update the mmc instances on l3 interconnect to probe properly with
      ti-sysc interconnect target module driver to make mmc3 work again. Let's
      still keep legacy "ti,hwmods" property around for v5.2 kernel and only
      drop it later on.
      Note that there is no need to use property status = "disabled" for mmc3.
      The default for dts is enabled, and runtime PM will idle unused instances
      just fine.
      Fixes: 4e27f752 ("ARM: OMAP2+: Drop mmc platform data for am330x and am43xx")
      Reported-by: default avatarDavid Lechner <david@lechnology.com>
      Tested-by: default avatarDavid Lechner <david@lechnology.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
    • Tony Lindgren's avatar
      Merge branch 'ti-sysc-fixes' into fixes · 58e16d79
      Tony Lindgren authored
    • Suman Anna's avatar
      bus: ti-sysc: Simplify cleanup upon failures in sysc_probe() · a304f483
      Suman Anna authored
      The clocks are not yet parsed and prepared until after a successful
      sysc_get_clocks(), so there is no need to unprepare the clocks upon
      any failure of any of the prior functions in sysc_probe(). The current
      code path would have been a no-op because of the clock validity checks
      within sysc_unprepare(), but let's just simplify the cleanup path by
      returning the error directly.
      While at this, also fix the cleanup path for a sysc_init_resets()
      failure which is executed after the clocks are prepared.
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
    • Janusz Krzysztofik's avatar
      ARM: OMAP1: ams-delta-fiq: Fix missing irq_ack · fa8397e4
      Janusz Krzysztofik authored
      Non-serio path of Amstrad Delta FIQ deferred handler depended on
      irq_ack() method provided by OMAP GPIO driver.  That method has been
      removed by commit 693de831 ("gpio: omap: remove irq_ack method").
      Remove useless code from the deferred handler and reimplement the
      missing operation inside the base FIQ handler.
      Should another dependency - irq_unmask() - be ever removed from the OMAP
      GPIO driver, WARN once if missing.
      Signed-off-by: default avatarJanusz Krzysztofik <jmkrzyszt@gmail.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
    • Faiz Abbas's avatar
      ARM: dts: dra74x: Fix iodelay configuration for mmc3 · 07f9a8be
      Faiz Abbas authored
      According to the latest am572x[1] and dra74x[2] data manuals, mmc3
      default, hs, sdr12 and sdr25 modes use iodelay values given in
      MMC3_MANUAL1. Set the MODE_SELECT bit for these so that manual mode is
      selected and correct iodelay values can be configured.
      [1] http://www.ti.com/lit/ds/symlink/am5728.pdf
      [2] http://www.ti.com/lit/ds/symlink/dra746.pdfSigned-off-by: default avatarFaiz Abbas <faiz_abbas@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
    • Emmanuel Vadot's avatar
      ARM: dts: am335x: Fix UARTs length · 8613e2ca
      Emmanuel Vadot authored
      As seen on the AM335x TRM all the UARTs controller only are 0x1000 in size.
      Fix this in the DTS.
      Signed-off-by: default avatarEmmanuel Vadot <manu@freebsd.org>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
    • Tony Lindgren's avatar
      ARM: OMAP2+: Fix omap4 errata warning on other SoCs · 45da5e09
      Tony Lindgren authored
      We have errata i688 workaround produce warnings on SoCs other than
      omap4 and omap5:
      omap4_sram_init:Unable to allocate sram needed to handle errata I688
      omap4_sram_init:Unable to get sram pool needed to handle errata I688
      This is happening because there is no ti,omap4-mpu node, or no SRAM
      to configure for the other SoCs, so let's remove the warning based
      on the SoC revision checks.
      As nobody has complained it seems that the other SoC variants do not
      need this workaround.
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
    • John Garry's avatar
      bus: hisi_lpc: Add .remove method to avoid driver unbind crash · 10e62b47
      John Garry authored
      The original driver author seemed to be under the impression that a driver
      cannot be removed if it does not have a .remove method. Or maybe if it is
      a built-in platform driver.
      This is not true. This crash can be created:
      root@ubuntu:/sys/bus/platform/drivers/hisi-lpc# echo HISI0191\:00 > unbind
      root@ubuntu:/sys/bus/platform/drivers/hisi-lpc# ipmitool raw 6 1
       Unable to handle kernel paging request at virtual address ffff000010035010
       Mem abort info:
         ESR = 0x96000047
         Exception class = DABT (current EL), IL = 32 bits
         SET = 0, FnV = 0
         EA = 0, S1PTW = 0
       Data abort info:
         ISV = 0, ISS = 0x00000047
         CM = 0, WnR = 1
       swapper pgtable: 4k pages, 48-bit VAs, pgdp=000000000118b000
       [ffff000010035010] pgd=0000041ffbfff003, pud=0000041ffbffe003, pmd=0000041ffbffd003, pte=0000000000000000
       Internal error: Oops: 96000047 [#1] PREEMPT SMP
       Modules linked in:
       CPU: 17 PID: 1473 Comm: ipmitool Not tainted 5.2.0-rc5-00003-gf68c53b414a3-dirty #198
       Hardware name: Huawei Taishan 2280 /D05, BIOS Hisilicon D05 IT21 Nemo 2.0 RC0 04/18/2018
       pstate: 20000085 (nzCv daIf -PAN -UAO)
       pc : hisi_lpc_target_in+0x7c/0x120
       lr : hisi_lpc_target_in+0x70/0x120
       sp : ffff00001efe3930
       x29: ffff00001efe3930 x28: ffff841f9f599200
       x27: 0000000000000002 x26: 0000000000000000
       x25: 0000000000000080 x24: 00000000000000e4
       x23: 0000000000000000 x22: 0000000000000064
       x21: ffff801fb667d280 x20: 0000000000000001
       x19: ffff00001efe39ac x18: 0000000000000000
       x17: 0000000000000000 x16: 0000000000000000
       x15: 0000000000000000 x14: 0000000000000000
       x13: 0000000000000000 x12: 0000000000000000
       x11: 0000000000000000 x10: 0000000000000000
       x9 : 0000000000000000 x8 : ffff841febe60340
       x7 : ffff801fb55c52e8 x6 : 0000000000000000
       x5 : 0000000000ffc0e3 x4 : 0000000000000001
       x3 : ffff801fb667d280 x2 : 0000000000000001
       x1 : ffff000010035010 x0 : ffff000010035000
       Call trace:
       Code: 941d1511 aa0003f9 f94006a0 91004001 (b9000034)
       ---[ end trace aa842b86af7069e4 ]---
      The problem here is that the host goes away but the associated logical PIO
      region remains registered, as do the children devices.
      Fix by adding a .remove method to tidy-up by removing the child devices
      and unregistering the logical PIO region.
      Cc: stable@vger.kernel.org
      Fixes: adf38bb0 ("HISI LPC: Support the LPC host on Hip06/Hip07 with DT bindings")
      Signed-off-by: default avatarJohn Garry <john.garry@huawei.com>
      Signed-off-by: default avatarWei Xu <xuwei5@hisilicon.com>
    • John Garry's avatar
      bus: hisi_lpc: Unregister logical PIO range to avoid potential use-after-free · 1b15a563
      John Garry authored
      If, after registering a logical PIO range, the driver probe later fails,
      the logical PIO range memory will be released automatically.
      This causes an issue, in that the logical PIO range is not unregistered
      and the released range memory may be later referenced.
      Fix by unregistering the logical PIO range.
      And since we now unregister the logical PIO range for probe failure, avoid
      the special ordering of setting logical PIO range ops, which was the
      previous (poor) attempt at a safeguard against this.
      Cc: stable@vger.kernel.org
      Fixes: adf38bb0 ("HISI LPC: Support the LPC host on Hip06/Hip07 with DT bindings")
      Signed-off-by: default avatarJohn Garry <john.garry@huawei.com>
      Signed-off-by: default avatarWei Xu <xuwei5@hisilicon.com>
    • John Garry's avatar
      lib: logic_pio: Add logic_pio_unregister_range() · b884e2de
      John Garry authored
      Add a function to unregister a logical PIO range.
      Logical PIO space can still be leaked when unregistering certain
      LOGIC_PIO_CPU_MMIO regions, but this acceptable for now since there are no
      callers to unregister LOGIC_PIO_CPU_MMIO regions, and the logical PIO
      region allocation scheme would need significant work to improve this.
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarJohn Garry <john.garry@huawei.com>
      Signed-off-by: default avatarWei Xu <xuwei5@hisilicon.com>
    • John Garry's avatar
      lib: logic_pio: Avoid possible overlap for unregistering regions · 0a27142b
      John Garry authored
      The code was originally written to not support unregistering logical PIO
      To accommodate supporting unregistering logical PIO regions, subtly modify
      LOGIC_PIO_CPU_MMIO region registration code, such that the "end" of the
      registered regions is the "end" of the last region, and not the sum of
      the sizes of all the registered regions.
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarJohn Garry <john.garry@huawei.com>
      Signed-off-by: default avatarWei Xu <xuwei5@hisilicon.com>
    • John Garry's avatar
      lib: logic_pio: Fix RCU usage · 06709e81
      John Garry authored
      The traversing of io_range_list with list_for_each_entry_rcu()
      is not properly protected by rcu_read_lock() and rcu_read_unlock(),
      so add them.
      These functions mark the critical section scope where the list is
      protected for the reader, it cannot be  "reclaimed". Any updater - in
      this case, the logical PIO registration functions - cannot update the
      list until the reader exits this critical section.
      In addition, the list traversing used in logic_pio_register_range()
      does not need to use the rcu variant.
      This is because we are already using io_range_mutex to guarantee mutual
      exclusion from mutating the list.
      Cc: stable@vger.kernel.org
      Fixes: 031e3601 ("lib: Add generic PIO mapping method")
      Signed-off-by: default avatarJohn Garry <john.garry@huawei.com>
      Signed-off-by: default avatarWei Xu <xuwei5@hisilicon.com>
  4. 11 Aug, 2019 3 commits
  5. 10 Aug, 2019 15 commits
    • Linus Torvalds's avatar
      Merge tag 'riscv/for-v5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux · 296d05cb
      Linus Torvalds authored
      Pull RISC-V updates from Paul Walmsley:
       "A few minor RISC-V updates for v5.3-rc4:
         - Remove __udivdi3() from the 32-bit Linux port, converting the only
           upstream user to use do_div(), per Linux policy
         - Convert the RISC-V standard clocksource away from per-cpu data
           structures, since only one is used by Linux, even on a multi-CPU
         - A set of DT binding updates that remove an obsolete text binding in
           favor of a YAML binding, fix a bogus compatible string in the
           schema (thus fixing a "make dtbs_check" warning), and clarifies the
           future values expected in one of the RISC-V CPU properties"
      * tag 'riscv/for-v5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux:
        dt-bindings: riscv: fix the schema compatible string for the HiFive Unleashed board
        dt-bindings: riscv: remove obsolete cpus.txt
        RISC-V: Remove udivdi3
        riscv: delay: use do_div() instead of __udivdi3()
        dt-bindings: Update the riscv,isa string description
        RISC-V: Remove per cpu clocksource
    • Linus Torvalds's avatar
      Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip · 6d8f809c
      Linus Torvalds authored
      Pull x86 fixes from Thomas Gleixner:
       "A few fixes for x86:
         - Don't reset the carefully adjusted build flags for the purgatory
           and remove the unwanted flags instead. The 'reset all' approach led
           to build fails under certain circumstances.
         - Unbreak CLANG build of the purgatory by avoiding the builtin
           memcpy/memset implementations.
         - Address missing prototype warnings by including the proper header
         - Fix yet more fall-through issues"
      * 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
        x86/lib/cpu: Address missing prototypes warning
        x86/purgatory: Use CFLAGS_REMOVE rather than reset KBUILD_CFLAGS
        x86/purgatory: Do not use __builtin_memcpy and __builtin_memset
        x86: mtrr: cyrix: Mark expected switch fall-through
        x86/ptrace: Mark expected switch fall-through
    • Linus Torvalds's avatar
      Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip · d2359a51
      Linus Torvalds authored
      Pull perf tooling fixes from Thomas Gleixner:
       "Perf tooling fixes all over the place:
         - Fix the selection of the main thread COMM in db-export
         - Fix the disassemmbly display for BPF in annotate
         - Fix cpumap mask setup in perf ftrace when only one CPU is present
         - Add the missing 'cpu_clk_unhalted.core' event
         - Fix CPU 0 bindings in NUMA benchmarks
         - Fix the module size calculations for s390
         - Handle the gap between kernel end and module start on s390
         - Build and typo fixes"
      * 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
        perf pmu-events: Fix missing "cpu_clk_unhalted.core" event
        perf annotate: Fix s390 gap between kernel end and module start
        perf record: Fix module size on s390
        perf tools: Fix include paths in ui directory
        perf tools: Fix a typo in a variable name in the Documentation Makefile
        perf cpumap: Fix writing to illegal memory in handling cpumap mask
        perf ftrace: Fix failure to set cpumask when only one cpu is present
        perf db-export: Fix thread__exec_comm()
        perf annotate: Fix printing of unaugmented disassembled instructions from BPF
        perf bench numa: Fix cpu0 binding
    • Linus Torvalds's avatar
      Merge branch 'sched-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip · dcbb4a15
      Linus Torvalds authored
      Pull scheduler fixes from Thomas Gleixner:
       "Three fixlets for the scheduler:
         - Avoid double bandwidth accounting in the push & pull code
         - Use a sane FIFO priority for the Pressure Stall Information (PSI)
         - Avoid permission checks when setting the scheduler params for the
           PSI thread"
      * 'sched-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
        sched/psi: Do not require setsched permission from the trigger creator
        sched/psi: Reduce psimon FIFO priority
        sched/deadline: Fix double accounting of rq/running bw in push & pull
    • Linus Torvalds's avatar
      Merge branch 'irq-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip · ed254bb5
      Linus Torvalds authored
      Pull irq fix from Thomas Gleixner:
       "A small fix for the affinity spreading code.
        It failed to handle situations where a single vector was requested
        either due to only one CPU being available or vector exhaustion
        causing only a single interrupt to be granted.
        The fix is to simply remove the requirement in the affinity spreading
        code for more than one interrupt being available"
      * 'irq-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
        genirq/affinity: Create affinity mask for single vector
    • Linus Torvalds's avatar
      Merge branch 'core-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip · 6054f4ec
      Linus Torvalds authored
      Pull objtool warning fix from Thomas Gleixner:
       "The recent objtool fixes/enhancements unearthed a unbalanced CLAC in
        the i915 driver.
        Chris asked me to pick the fix up and route it through"
      * 'core-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
        drm/i915: Remove redundant user_access_end() from __copy_from_user() error path
    • Linus Torvalds's avatar
      Merge tag 'gfs2-v5.3-rc3.fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2 · 829890d2
      Linus Torvalds authored
      Pull gfs2 fix from Andreas Gruenbacher:
       "Fix incorrect lseek / fiemap results"
      * tag 'gfs2-v5.3-rc3.fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2:
        gfs2: gfs2_walk_metadata fix
    • Joe Perches's avatar
      Makefile: Convert -Wimplicit-fallthrough=3 to just -Wimplicit-fallthrough for clang · bfd77145
      Joe Perches authored
      A compilation -Wimplicit-fallthrough warning was enabled by commit
      a035d552 ("Makefile: Globally enable fall-through warning")
      Even though clang 10.0.0 does not currently support this warning without
      a patch, clang currently does not support a value for this option.
        Link: https://bugs.llvm.org/show_bug.cgi?id=39382
      The gcc default for this warning is 3 so removing the =3 has no effect
      for gcc and enables the warning for patched versions of clang.
      Also remove the =3 from an existing use in a parisc Makefile:
      Signed-off-by: default avatarJoe Perches <joe@perches.com>
      Reviewed-and-tested-by: default avatarNathan Chancellor <natechancellor@gmail.com>
      Cc: Gustavo A. R. Silva <gustavo@embeddedor.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
    • Linus Torvalds's avatar
      Merge tag 'char-misc-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc · 5aa91007
      Linus Torvalds authored
      Pull char/misc driver fixes Greg KH:
       "Here are some small char/misc driver fixes for 5.3-rc4.
        Two of these are for the habanalabs driver for issues found when
        running on a big-endian system (are they still alive?) The others are
        tiny fixes reported by people, and a MAINTAINERS update about the
        location of the fpga development tree.
        All of these have been in linux-next for a while with no reported
      * tag 'char-misc-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc:
        coresight: Fix DEBUG_LOCKS_WARN_ON for uninitialized attribute
        MAINTAINERS: Move linux-fpga tree to new location
        nvmem: Use the same permissions for eeprom as for nvmem
        habanalabs: fix host memory polling in BE architecture
        habanalabs: fix F/W download in BE architecture
    • Linus Torvalds's avatar
      Merge tag 'driver-core-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core · 36e630ed
      Linus Torvalds authored
      Pull driver core fixes from Greg KH:
       "Here are two small fixes for some driver core issues that have been
        reported. There is also a kernfs "fix" here, which was then reverted
        because it was found to cause problems in linux-next.
        The driver core fixes both resolve reported issues, one with gpioint
        stuff that showed up in 5.3-rc1, and the other finally (and hopefully)
        resolves a very long standing race when removing glue directories.
        It's nice to get that issue finally resolved and the developers
        involved should be applauded for the persistence it took to get this
        patch finally accepted.
        All of these have been in linux-next for a while with no reported
        issues. Well, the one reported issue, hence the revert :)"
      * tag 'driver-core-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core:
        Revert "kernfs: fix memleak in kernel_ops_readdir()"
        kernfs: fix memleak in kernel_ops_readdir()
        driver core: Fix use-after-free and double free on glue directory
        driver core: platform: return -ENXIO for missing GpioInt
    • Linus Torvalds's avatar
      Merge tag 'tty-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty · c13f8670
      Linus Torvalds authored
      Pull tty fix from Greg KH:
       "Here is a single tty kgdb fix for 5.3-rc4.
        It fixes an annoying log message that has caused kdb to become
        useless. It's another fallout from commit ddde3c18 ("vt: More
        locking checks") which tries to enforce locking checks more strictly
        in the tty layer, unfortunatly when kdb is stopped, there's no need
        for locks :)
        This patch has been linux-next for a while with no reported issues"
      * tag 'tty-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty:
        kgdboc: disable the console lock when in kgdb
    • Linus Torvalds's avatar
      Merge tag 'staging-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging · 15fa98e4
      Linus Torvalds authored
      Pull staging / IIO driver fixes from Greg KH:
       "Here are some small staging and IIO driver fixes for 5.3-rc4.
        Nothing major, just resolutions for a number of small reported issues,
        full details in the shortlog.
        All have been in linux-next for a while with no reported issues"
      * tag 'staging-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging:
        iio: adc: gyroadc: fix uninitialized return code
        docs: generic-counter.rst: fix broken references for ABI file
        staging: android: ion: Bail out upon SIGKILL when allocating memory.
        Staging: fbtft: Fix GPIO handling
        staging: unisys: visornic: Update the description of 'poll_for_irq()'
        staging: wilc1000: flush the workqueue before deinit the host
        staging: gasket: apex: fix copy-paste typo
        Staging: fbtft: Fix reset assertion when using gpio descriptor
        Staging: fbtft: Fix probing of gpio descriptor
        iio: imu: mpu6050: add missing available scan masks
        iio: cros_ec_accel_legacy: Fix incorrect channel setting
        IIO: Ingenic JZ47xx: Set clock divider on probe
        iio: adc: max9611: Fix misuse of GENMASK macro
    • Linus Torvalds's avatar
      Merge tag 'usb-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb · 1041f509
      Linus Torvalds authored
      Pull USB fixes from Greg KH:
       "Here are some small USB fixes for 5.3-rc4.
        The "biggest" one here is moving code from one file to another in
        order to fix a long-standing race condition with the creation of sysfs
        files for USB devices. Turns out that there are now userspace tools
        out there that are hitting this long-known bug, so it's time to fix
        them. Thankfully the tool-maker in this case fixed the issue :)
        The other patches in here are all fixes for reported issues. Now that
        syzbot knows how to fuzz USB drivers better, and is starting to now
        fuzz the userspace facing side of them at the same time, there will be
        more and more small fixes like these coming, which is a good thing.
        All of these have been in linux-next with no reported issues"
      * tag 'usb-5.3-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb:
        usb: setup authorized_default attributes using usb_bus_notify
        usb: iowarrior: fix deadlock on disconnect
        Revert "USB: rio500: simplify locking"
        usb: usbfs: fix double-free of usb memory upon submiturb error
        usb: yurex: Fix use-after-free in yurex_delete
        usb: typec: tcpm: Ignore unsupported/unknown alternate mode requests
        xhci: Fix NULL pointer dereference at endpoint zero reset.
        usb: host: xhci-rcar: Fix timeout in xhci_suspend()
        usb: typec: ucsi: ccg: Fix uninitilized symbol error
        usb: typec: tcpm: remove tcpm dir if no children
        usb: typec: tcpm: free log buf memory when remove debug file
        usb: typec: tcpm: Add NULL check before dereferencing config
    • Linus Torvalds's avatar
      Merge tag 'pinctrl-v5.3-2' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl · 97946f59
      Linus Torvalds authored
      Pull pin control fixes from Linus Walleij:
       - Delay acquisition of regmaps in the Aspeed G5 driver.
       - Make a symbol static to reduce compiler noise.
      * tag 'pinctrl-v5.3-2' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl:
        pinctrl: aspeed: Make aspeed_pinmux_ips static
        pinctrl: aspeed-g5: Delay acquisition of regmaps
    • Linus Torvalds's avatar
      Merge tag 'powerpc-5.3-4' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux · 23df57af
      Linus Torvalds authored
      Pull powerpc fix from Michael Ellerman:
       "Just one fix, a revert of a commit that was meant to be a minor
        improvement to some inline asm, but ended up having no real benefit
        with GCC and broke booting 32-bit machines when using Clang.
        Thanks to: Arnd Bergmann, Christophe Leroy, Nathan Chancellor, Nick
        Desaulniers, Segher Boessenkool"
      * tag 'powerpc-5.3-4' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:
        Revert "powerpc: slightly improve cache helpers"