Forum | Documentation | Website | Blog

Skip to content
Snippets Groups Projects
  1. Dec 03, 2018
  2. Nov 25, 2018
  3. Nov 18, 2018
  4. Aug 17, 2018
  5. Mar 05, 2018
  6. Nov 09, 2017
  7. Sep 01, 2017
  8. Jul 25, 2017
  9. May 01, 2017
    • Hans-Christian Noren Egtvedt's avatar
      avr32: remove support for AVR32 architecture · 26202873
      Hans-Christian Noren Egtvedt authored
      
      This patch drops support for AVR32 architecture from the Linux kernel.
      
      The AVR32 architecture is not keeping up with the development of the
      kernel, and since it shares so much of the drivers with Atmel ARM SoC,
      it is starting to hinder these drivers to develop swiftly.
      
      Also, all AVR32 AP7 SoC processors are end of lifed from Atmel (now
      Microchip).
      
      Finally, the GCC toolchain is stuck at version 4.2.x, and has not
      received any patches since the last release from Atmel;
      4.2.4-atmel.1.1.3.avr32linux.1. When building kernel v4.10, this
      toolchain is no longer able to properly link the network stack.
      
      Haavard and I have came to the conclusion that we feel keeping AVR32 on
      life support offers more obstacles for Atmel ARMs, than it gives joy to
      AVR32 users. I also suspect there are very few AVR32 users left today,
      if anybody at all.
      
      Signed-off-by: default avatarHans-Christian Noren Egtvedt <egtvedt@samfundet.no>
      Signed-off-by: default avatarHåvard Skinnemoen <hskinnemoen@gmail.com>
      Signed-off...
      26202873
  10. Feb 13, 2017
  11. Dec 21, 2016
  12. Dec 02, 2016
  13. Oct 27, 2016
  14. Oct 25, 2016
  15. Oct 07, 2016
  16. Sep 19, 2016
  17. Sep 09, 2016
  18. Sep 01, 2016
  19. Aug 31, 2016
  20. Jun 15, 2016
  21. Jun 14, 2016
  22. Mar 29, 2016
    • Linus Walleij's avatar
      Documentation: update the devices.txt documentation · ebdf4040
      Linus Walleij authored
      
      Alan is no longer maintaining this list through the Linux assigned
      numbers authority. Make it a collective document by referring to
      "the maintainers" in plural throughout, and naming the chardev and
      block layer maintainers in particular as parties of involvement.
      Cut down and remove some sections that pertained to the process of
      maintaining the list at lanana.org and contacting Alan directly.
      
      Make it clear that this document, in the kernel, is the master
      document.
      
      Also move paragraphs around so as to emphasize dynamic major number
      allocation.
      
      Remove paragraph on 2.6 deprecation, that tag no longer appears
      anywhere in the file.
      
      Cc: Jonathan Corbet <corbet@lwn.net>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Alan Cox <alan@linux.intel.com>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Jens Axboe <axboe@kernel.dk>
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      ebdf4040
  23. Jan 24, 2016
  24. Jan 20, 2016
  25. Jan 13, 2016
  26. Dec 18, 2015
  27. Sep 10, 2015
  28. Jul 28, 2015
  29. Jul 14, 2015
    • Aleksa Sarai's avatar
      cgroup: implement the PIDs subsystem · 49b786ea
      Aleksa Sarai authored
      
      Adds a new single-purpose PIDs subsystem to limit the number of
      tasks that can be forked inside a cgroup. Essentially this is an
      implementation of RLIMIT_NPROC that applies to a cgroup rather than a
      process tree.
      
      However, it should be noted that organisational operations (adding and
      removing tasks from a PIDs hierarchy) will *not* be prevented. Rather,
      the number of tasks in the hierarchy cannot exceed the limit through
      forking. This is due to the fact that, in the unified hierarchy, attach
      cannot fail (and it is not possible for a task to overcome its PIDs
      cgroup policy limit by attaching to a child cgroup -- even if migrating
      mid-fork it must be able to fork in the parent first).
      
      PIDs are fundamentally a global resource, and it is possible to reach
      PID exhaustion inside a cgroup without hitting any reasonable kmemcg
      policy. Once you've hit PID exhaustion, you're only in a marginally
      better state than OOM. This subsystem allows PID exhaustion inside a
      cgroup to be prevented.
      
      Signed-off-by: default avatarAleksa Sarai <cyphar@cyphar.com>
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      49b786ea
  30. Jun 30, 2015
  31. Jun 23, 2015
  32. May 07, 2015
  33. Apr 21, 2015
  34. Apr 15, 2015
  35. Mar 23, 2015
  36. Dec 19, 2014
  37. Aug 08, 2014
  38. Jul 30, 2014