1. 27 May, 2021 2 commits
  2. 01 May, 2021 1 commit
  3. 16 Apr, 2021 1 commit
  4. 23 Mar, 2021 1 commit
  5. 21 Dec, 2020 1 commit
  6. 03 Dec, 2020 1 commit
  7. 26 Nov, 2020 4 commits
  8. 19 Nov, 2020 1 commit
  9. 18 Nov, 2020 1 commit
  10. 08 Oct, 2020 1 commit
  11. 04 Oct, 2020 2 commits
  12. 08 Sep, 2020 1 commit
  13. 24 Aug, 2020 2 commits
  14. 29 Jul, 2020 2 commits
  15. 22 Jul, 2020 1 commit
  16. 30 Jun, 2020 2 commits
  17. 22 Jun, 2020 1 commit
  18. 28 May, 2020 3 commits
  19. 20 May, 2020 1 commit
  20. 18 May, 2020 1 commit
  21. 11 May, 2020 1 commit
  22. 27 Mar, 2020 1 commit
  23. 25 Mar, 2020 1 commit
  24. 04 Mar, 2020 1 commit
  25. 03 Feb, 2020 1 commit
    • Masahiro Yamada's avatar
      kbuild: rename hostprogs-y/always to hostprogs/always-y · 5f2fb52f
      Masahiro Yamada authored
      
      
      In old days, the "host-progs" syntax was used for specifying host
      programs. It was renamed to the current "hostprogs-y" in 2004.
      
      It is typically useful in scripts/Makefile because it allows Kbuild to
      selectively compile host programs based on the kernel configuration.
      
      This commit renames like follows:
      
        always       ->  always-y
        hostprogs-y  ->  hostprogs
      
      So, scripts/Makefile will look like this:
      
        always-$(CONFIG_BUILD_BIN2C) += ...
        always-$(CONFIG_KALLSYMS)    += ...
            ...
        hostprogs := $(always-y) $(always-m)
      
      I think this makes more sense because a host program is always a host
      program, irrespective of the kernel configuration. We want to specify
      which ones to compile by CONFIG options, so always-y will be handier.
      
      The "always", "hostprogs-y", "hostprogs-m" will be kept for backward
      compatibility for a while.
      
      Signed-off-by: default avatarMasahiro Yamada <masahiroy@kernel.org>
      5f2fb52f
  26. 23 Jan, 2020 2 commits
  27. 06 Jan, 2020 1 commit
  28. 26 Nov, 2019 1 commit
    • Masahiro Yamada's avatar
      libfdt: define INT32_MAX and UINT32_MAX in libfdt_env.h · a8de1304
      Masahiro Yamada authored
      
      
      The DTC v1.5.1 added references to (U)INT32_MAX.
      
      This is no problem for user-space programs since <stdint.h> defines
      (U)INT32_MAX along with (u)int32_t.
      
      For the kernel space, libfdt_env.h needs to be adjusted before we
      pull in the changes.
      
      In the kernel, we usually use s/u32 instead of (u)int32_t for the
      fixed-width types.
      
      Accordingly, we already have S/U32_MAX for their max values.
      So, we should not add (U)INT32_MAX to <linux/limits.h> any more.
      
      Instead, add them to the in-kernel libfdt_env.h to compile the
      latest libfdt.
      
      Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
      Signed-off-by: default avatarRob Herring <robh@kernel.org>
      a8de1304
  29. 17 Nov, 2019 1 commit