All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: [GIT PULL 1/2] Kbuild updates for v5.11-rc1
Date: Wed, 23 Dec 2020 01:45:59 +0900	[thread overview]
Message-ID: <CAK7LNAQbWcXRFd55DkUVrcr9Z2yjUOV-3qnkjrjr3VOC5JDOXA@mail.gmail.com> (raw)

Hi Linus,

Please pull Kbuild updates for v5.11

Thanks.


The following changes since commit 0477e92881850d44910a7e94fc2c46f96faa131f:

  Linux 5.10-rc7 (2020-12-06 14:25:12 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git
tags/kbuild-v5.11

for you to fetch changes up to 18084e435ff6e47197542db6bab98bafaa4c7b68:

  Documentation/kbuild: Document platform dependency practises
(2020-12-21 13:57:08 +0900)

----------------------------------------------------------------
Kbuild updates for v5.11

 - Use /usr/bin/env for shebang lines in scripts

 - Remove useless -Wnested-externs warning flag

 - Update documents

 - Refactor log handling in modpost

 - Stop building modules without MODULE_LICENSE() tag

 - Make the insane combination of 'static' and EXPORT_SYMBOL an error

 - Improve genksyms to handle _Static_assert()

----------------------------------------------------------------
Arnd Bergmann (1):
      Makefile.extrawarn: remove -Wnested-externs warning

Dominique Martinet (1):
      kbuild: don't hardcode depmod path

Finn Behrens (1):
      tweewide: Fix most Shebang lines

Geert Uytterhoeven (2):
      Documentation/kbuild: Document COMPILE_TEST dependencies
      Documentation/kbuild: Document platform dependency practises

Marco Elver (1):
      genksyms: Ignore module scoped _Static_assert()

Masahiro Yamada (12):
      kbuild: doc: update the description about kbuild Makefiles
      kbuild: doc: replace arch/$(ARCH)/ with arch/$(SRCARCH)/
      kbuild: doc: fix 'List directories to visit when descending' section
      kbuild: doc: merge 'Special Rules' and 'Custom kbuild commands' sections
      kbuild: doc: split if_changed explanation to a separate section
      kbuild: doc: clarify the difference between extra-y and always-y
      kbuild: doc: document subdir-y syntax
      modpost: rename merror() to error()
      modpost: refactor error handling and clarify error/fatal difference
      modpost: turn missing MODULE_LICENSE() into error
      modpost: change license incompatibility to error() from fatal()
      modpost: turn section mismatches to error from fatal()

Quentin Perret (1):
      modpost: turn static exports into error

 Documentation/kbuild/kconfig-language.rst         |  35 ++
 Documentation/kbuild/makefiles.rst                | 365 +++++++++++---------
 Documentation/kbuild/modules.rst                  |   2 +-
 Documentation/sphinx/parse-headers.pl             |   2 +-
 Documentation/target/tcm_mod_builder.py           |   2 +-
 Documentation/trace/postprocess/decode_msr.py     |   2 +-
 .../postprocess/trace-pagealloc-postprocess.pl    |   2 +-
 .../trace/postprocess/trace-vmscan-postprocess.pl |   2 +-
 Makefile                                          |   2 +-
 arch/ia64/scripts/unwcheck.py                     |   2 +-
 scripts/Makefile.extrawarn                        |   1 -
 scripts/bloat-o-meter                             |   2 +-
 scripts/config                                    |   2 +-
 scripts/diffconfig                                |   2 +-
 scripts/genksyms/keywords.c                       |   3 +
 scripts/genksyms/lex.l                            |  27 +-
 scripts/genksyms/parse.y                          |   7 +
 scripts/get_abi.pl                                |   2 +-
 scripts/mod/modpost.c                             |  73 ++--
 scripts/mod/modpost.h                             |  15 +-
 scripts/show_delta                                |   2 +-
 scripts/sphinx-pre-install                        |   2 +-
 scripts/split-man.pl                              |   2 +-
 scripts/tracing/draw_functrace.py                 |   2 +-
 tools/perf/python/tracepoint.py                   |   2 +-
 tools/perf/python/twatch.py                       |   2 +-
 .../intel_pstate_tracer/intel_pstate_tracer.py    |   2 +-
 tools/testing/ktest/compare-ktest-sample.pl       |   2 +-
 tools/testing/kunit/kunit.py                      |   2 +-
 tools/testing/kunit/kunit_tool_test.py            |   2 +-
 tools/testing/selftests/bpf/test_offload.py       |   2 +-
 .../net/mlxsw/sharedbuffer_configuration.py       |   2 +-
 tools/testing/selftests/kselftest/prefix.pl       |   2 +-
 tools/testing/selftests/net/devlink_port_split.py |   2 +-
 tools/testing/selftests/tc-testing/tdc_batch.py   |   2 +-
 .../selftests/tc-testing/tdc_multibatch.py        |   2 +-
 36 files changed, 353 insertions(+), 229 deletions(-)


-- 
Best Regards
Masahiro Yamada

             reply	other threads:[~2020-12-22 16:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 16:45 Masahiro Yamada [this message]
2020-12-22 22:24 ` [GIT PULL 1/2] Kbuild updates for v5.11-rc1 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAK7LNAQbWcXRFd55DkUVrcr9Z2yjUOV-3qnkjrjr3VOC5JDOXA@mail.gmail.com \
    --to=masahiroy@kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.