Skip to content
Snippets Groups Projects
  1. Jul 15, 2019
  2. Jun 08, 2019
    • Mauro Carvalho Chehab's avatar
      docs: mark orphan documents as such · 27c054d2
      Mauro Carvalho Chehab authored
      
      Sphinx doesn't like orphan documents:
      
          Documentation/accelerators/ocxl.rst: WARNING: document isn't included in any toctree
          Documentation/arm/stm32/overview.rst: WARNING: document isn't included in any toctree
          Documentation/arm/stm32/stm32f429-overview.rst: WARNING: document isn't included in any toctree
          Documentation/arm/stm32/stm32f746-overview.rst: WARNING: document isn't included in any toctree
          Documentation/arm/stm32/stm32f769-overview.rst: WARNING: document isn't included in any toctree
          Documentation/arm/stm32/stm32h743-overview.rst: WARNING: document isn't included in any toctree
          Documentation/arm/stm32/stm32mp157-overview.rst: WARNING: document isn't included in any toctree
          Documentation/gpu/msm-crash-dump.rst: WARNING: document isn't included in any toctree
          Documentation/interconnect/interconnect.rst: WARNING: document isn't included in any toctree
          Documentation/laptops/lg-laptop.rst: WARNING: document isn't included in any toctree
          Documentation/powerpc/isa-versions.rst: WARNING: document isn't included in any toctree
          Documentation/virtual/kvm/amd-memory-encryption.rst: WARNING: document isn't included in any toctree
          Documentation/virtual/kvm/vcpu-requests.rst: WARNING: document isn't included in any toctree
      
      So, while they aren't on any toctree, add :orphan: to them, in order
      to silent this warning.
      
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab+samsung@kernel.org>
      Acked-by: default avatarAndrew Donnellan <ajd@linux.ibm.com>
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      27c054d2
  3. Jun 07, 2019
  4. Feb 12, 2019
    • Nathan Chancellor's avatar
      ARM: 8833/1: Ensure that NEON code always compiles with Clang · de9c0d49
      Nathan Chancellor authored
      While building arm32 allyesconfig, I ran into the following errors:
      
        arch/arm/lib/xor-neon.c:17:2: error: You should compile this file with
        '-mfloat-abi=softfp -mfpu=neon'
      
        In file included from lib/raid6/neon1.c:27:
        /home/nathan/cbl/prebuilt/lib/clang/8.0.0/include/arm_neon.h:28:2:
        error: "NEON support not enabled"
      
      Building V=1 showed NEON_FLAGS getting passed along to Clang but
      __ARM_NEON__ was not getting defined. Ultimately, it boils down to Clang
      only defining __ARM_NEON__ when targeting armv7, rather than armv6k,
      which is the '-march' value for allyesconfig.
      
      >From lib/Basic/Targets/ARM.cpp in the Clang source:
      
        // This only gets set when Neon instructions are actually available, unlike
        // the VFP define, hence the soft float and arch check. This is subtly
        // different from gcc, we follow the intent which was that it should be set
        // when Neon instructions are actually available.
        if ((FPU & NeonFPU) && !SoftFloat && ArchVersion >= 7) {
          Builder.defineMacro("__ARM_NEON", "1");
          Builder.defineMacro("__ARM_NEON__");
          // current AArch32 NEON implementations do not support double-precision
          // floating-point even when it is present in VFP.
          Builder.defineMacro("__ARM_NEON_FP",
                              "0x" + Twine::utohexstr(HW_FP & ~HW_FP_DP));
        }
      
      Ard Biesheuvel recommended explicitly adding '-march=armv7-a' at the
      beginning of the NEON_FLAGS definitions so that __ARM_NEON__ always gets
      definined by Clang. This doesn't functionally change anything because
      that code will only run where NEON is supported, which is implicitly
      armv7.
      
      Link: https://github.com/ClangBuiltLinux/linux/issues/287
      
      
      
      Suggested-by: default avatarArd Biesheuvel <ard.biesheuvel@linaro.org>
      Signed-off-by: default avatarNathan Chancellor <natechancellor@gmail.com>
      Acked-by: default avatarNicolas Pitre <nico@linaro.org>
      Reviewed-by: default avatarNick Desaulniers <ndesaulniers@google.com>
      Reviewed-by: default avatarStefan Agner <stefan@agner.ch>
      Signed-off-by: default avatarRussell King <rmk+kernel@armlinux.org.uk>
      de9c0d49
  5. Nov 20, 2018
    • Will Deacon's avatar
      Documentation: Use "while" instead of "whilst" · 806654a9
      Will Deacon authored
      
      Whilst making an unrelated change to some Documentation, Linus sayeth:
      
        | Afaik, even in Britain, "whilst" is unusual and considered more
        | formal, and "while" is the common word.
        |
        | [...]
        |
        | Can we just admit that we work with computers, and we don't need to
        | use þe eald Englisc spelling of words that most of the world never
        | uses?
      
      dictionary.com refers to the word as "Chiefly British", which is
      probably an undesirable attribute for technical documentation.
      
      Replace all occurrences under Documentation/ with "while".
      
      Cc: David Howells <dhowells@redhat.com>
      Cc: Liam Girdwood <lgirdwood@gmail.com>
      Cc: Chris Wilson <chris@chris-wilson.co.uk>
      Cc: Michael Halcrow <mhalcrow@google.com>
      Cc: Jonathan Corbet <corbet@lwn.net>
      Reported-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      Signed-off-by: default avatarWill Deacon <will.deacon@arm.com>
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      806654a9
  6. Sep 09, 2018
    • Henrik Austad's avatar
      Drop all 00-INDEX files from Documentation/ · a7ddcea5
      Henrik Austad authored
      
      This is a respin with a wider audience (all that get_maintainer returned)
      and I know this spams a *lot* of people. Not sure what would be the correct
      way, so my apologies for ruining your inbox.
      
      The 00-INDEX files are supposed to give a summary of all files present
      in a directory, but these files are horribly out of date and their
      usefulness is brought into question. Often a simple "ls" would reveal
      the same information as the filenames are generally quite descriptive as
      a short introduction to what the file covers (it should not surprise
      anyone what Documentation/sched/sched-design-CFS.txt covers)
      
      A few years back it was mentioned that these files were no longer really
      needed, and they have since then grown further out of date, so perhaps
      it is time to just throw them out.
      
      A short status yields the following _outdated_ 00-INDEX files, first
      counter is files listed in 00-INDEX but missing in the directory, last
      is files present but not listed in 00-INDEX.
      
      List of outdated 00-INDEX:
      Documentation: (4/10)
      Documentation/sysctl: (0/1)
      Documentation/timers: (1/0)
      Documentation/blockdev: (3/1)
      Documentation/w1/slaves: (0/1)
      Documentation/locking: (0/1)
      Documentation/devicetree: (0/5)
      Documentation/power: (1/1)
      Documentation/powerpc: (0/5)
      Documentation/arm: (1/0)
      Documentation/x86: (0/9)
      Documentation/x86/x86_64: (1/1)
      Documentation/scsi: (4/4)
      Documentation/filesystems: (2/9)
      Documentation/filesystems/nfs: (0/2)
      Documentation/cgroup-v1: (0/2)
      Documentation/kbuild: (0/4)
      Documentation/spi: (1/0)
      Documentation/virtual/kvm: (1/0)
      Documentation/scheduler: (0/2)
      Documentation/fb: (0/1)
      Documentation/block: (0/1)
      Documentation/networking: (6/37)
      Documentation/vm: (1/3)
      
      Then there are 364 subdirectories in Documentation/ with several files that
      are missing 00-INDEX alltogether (and another 120 with a single file and no
      00-INDEX).
      
      I don't really have an opinion to whether or not we /should/ have 00-INDEX,
      but the above 00-INDEX should either be removed or be kept up to date. If
      we should keep the files, I can try to keep them updated, but I rather not
      if we just want to delete them anyway.
      
      As a starting point, remove all index-files and references to 00-INDEX and
      see where the discussion is going.
      
      Signed-off-by: default avatarHenrik Austad <henrik@austad.us>
      Acked-by: default avatar"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
      Just-do-it-by: default avatarSteven Rostedt <rostedt@goodmis.org>
      Reviewed-by: default avatarJens Axboe <axboe@kernel.dk>
      Acked-by: default avatarPaul Moore <paul@paul-moore.com>
      Acked-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Acked-by: default avatarMark Brown <broonie@kernel.org>
      Acked-by: default avatarMike Rapoport <rppt@linux.vnet.ibm.com>
      Cc: [Almost everybody else]
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      a7ddcea5
  7. Aug 30, 2018
    • Krzysztof Kozlowski's avatar
      ARM: exynos: Fix imprecise abort during Exynos5422 suspend to RAM · e0b35c1a
      Krzysztof Kozlowski authored
      
      Suspend to RAM on Odroid XU3/XU4/HC1 family (Exynos5422) causes
      imprecise abort:
      
      	PM: Syncing filesystems ... done.
      	Freezing user space processes ... (elapsed 0.003 seconds) done.
      	OOM killer disabled.
      	Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
      	wake enabled for irq 139
      	Disabling non-boot CPUs ...
      	IRQ51 no longer affine to CPU1
      	IRQ52 no longer affine to CPU2
      	IRQ53 no longer affine to CPU3
      	IRQ54 no longer affine to CPU4
      	IRQ55 no longer affine to CPU5
      	IRQ56 no longer affine to CPU6
      	cpu cpu4: Dropping the link to regulator.40
      	IRQ57 no longer affine to CPU7
      	Unhandled fault: external abort on non-linefetch (0x1008) at 0xf081a028
      	Internal error: : 1008 [#1] PREEMPT SMP ARM
      
      with last call trace in exynos_suspend_enter().
      
      The abort is caused by writing to register in secure part of sysram.
      Boards booted under secure firmware (e.g. Hardkernel Odroid boards)
      should access non-secure sysram.
      
      Signed-off-by: default avatarKrzysztof Kozlowski <krzk@kernel.org>
      e0b35c1a
  8. May 16, 2018
  9. May 03, 2018
  10. Mar 06, 2018
  11. Mar 05, 2018
  12. Feb 28, 2018
  13. Feb 16, 2018
  14. Sep 22, 2017
  15. Jul 17, 2017
  16. Jun 02, 2017
  17. Apr 20, 2017
  18. Mar 24, 2017
  19. Jan 20, 2017
  20. Jan 02, 2017
  21. Nov 15, 2016
  22. Oct 24, 2016
  23. Oct 10, 2016
  24. Sep 08, 2016
  25. Aug 18, 2016
  26. Aug 17, 2016
    • Pawel Moll's avatar
      bus: arm-ccn: Correct required arguments for XP PMU events · 90d11e26
      Pawel Moll authored
      
      XP can provide events from two sources: watchpoints, observing traffic
      on device ports and PMU looking at internal buses.
      
      Unfortunately the sysfs definition of the PMU events was requiring
      port number (instead of bus number) and direction (the buses are
      unidirectional), as these fields were shared with the watchpoint event.
      
      Although it does not introduce a major problem (port can be used as
      bus alias and direction is simply ignored for XP PMU events), it's
      better to fix it now, before external tools start depending on this
      behaviour.
      
      Signed-off-by: default avatarPawel Moll <pawel.moll@arm.com>
      90d11e26
  27. Jun 21, 2016
  28. Apr 28, 2016
  29. Feb 19, 2016
  30. Feb 17, 2016
Loading