1. 15 1月, 2022 1 次提交
  2. 03 1月, 2022 1 次提交
  3. 26 12月, 2021 1 次提交
  4. 17 12月, 2021 1 次提交
  5. 11 12月, 2021 1 次提交
  6. 10 12月, 2021 1 次提交
  7. 08 12月, 2021 1 次提交
  8. 07 12月, 2021 1 次提交
  9. 03 12月, 2021 1 次提交
  10. 01 12月, 2021 1 次提交
  11. 30 11月, 2021 1 次提交
  12. 26 11月, 2021 2 次提交
  13. 25 11月, 2021 2 次提交
  14. 24 11月, 2021 1 次提交
  15. 22 11月, 2021 1 次提交
  16. 19 11月, 2021 2 次提交
  17. 17 11月, 2021 1 次提交
  18. 13 11月, 2021 1 次提交
    • S
      tools/lib/lockdep: drop liblockdep · 7246f4dc
      Sasha Levin 提交于
      TL;DR: While a tool like liblockdep is useful, it probably doesn't
      belong within the kernel tree.
      
      liblockdep attempts to reuse kernel code both directly (by directly
      building the kernel's lockdep code) as well as indirectly (by using
      sanitized headers). This makes liblockdep an integral part of the
      kernel.
      
      It also makes liblockdep quite unique: while other userspace code might
      use sanitized headers, it generally doesn't attempt to use kernel code
      directly which means that changes on the kernel side of things don't
      affect (and break) it directly.
      
      All our workflows and tooling around liblockdep don't support this
      uniqueness. Changes that go into the kernel code aren't validated to not
      break in-tree userspace code.
      
      liblockdep ended up being very fragile, breaking over and over, to the
      point that living in the same tree as the lockdep code lost most of it's
      value.
      
      liblockdep should continue living in an external tree, syncing with
      the kernel often, in a controllable way.
      Signed-off-by: NSasha Levin <sashal@kernel.org>
      Cc: Ingo Molnar <mingo@kernel.org>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      7246f4dc
  19. 10 11月, 2021 5 次提交
  20. 09 11月, 2021 1 次提交
  21. 07 11月, 2021 1 次提交
  22. 06 11月, 2021 1 次提交
  23. 05 11月, 2021 3 次提交
  24. 03 11月, 2021 2 次提交
  25. 01 11月, 2021 2 次提交
  26. 30 10月, 2021 3 次提交
  27. 29 10月, 2021 1 次提交