From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ak@linux.intel.com, andi@firstfloor.org, bp@suse.de,
fabio.estevam@freescale.com, jmario@redhat.com,
josh@joshtriplett.org, keescook@chromium.org, mmarek@suse.cz,
slyfox@gentoo.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT] kbuild changes for v3.13-rc1
Date: Fri, 15 Nov 2013 17:09:52 +0100 [thread overview]
Message-ID: <20131115160952.GA19669@sepie.suse.cz> (raw)
Hi Linus,
please pull these kbuild commits for v3.13-rc1:
- LTO fixes, but the kallsyms part had to be reverted
- -Werror=implicit-int and -Werror=strict-prototypes is passsed to the
compiler by default
- snprintf fix in modpost
- GREP_OPTIONS is removed from the environment to be immune against
exotic grep option settings
Thanks,
Michal
The following changes since commit 272b98c6455f00884f0350f775c5342358ebb73f:
Linux 3.12-rc1 (2013-09-16 16:17:51 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git kbuild
for you to fetch changes up to 480f439c3db0d45d817d66caf3fa8e81a6fac01a:
kallsyms: Revert back to 128 max symbol length (2013-11-13 15:58:19 +0100)
----------------------------------------------------------------
Andi Kleen (2):
Kbuild: Handle longer symbols in kallsyms.c
kbuild, bloat-o-meter: fix static detection
Borislav Petkov (1):
Kbuild: Ignore GREP_OPTIONS env variable
Fabio Estevam (1):
scripts: kallsyms: Use %zu to print 'size_t'
Joe Mario (1):
kbuild: Increase kallsyms max symbol length
Josh Triplett (2):
scripts/bloat-o-meter: ignore changes in the size of linux_banner
scripts/bloat-o-meter: use .startswith rather than fragile slicing
Kees Cook (1):
kbuild: replace unbounded sprintf call in modpost
Michal Marek (1):
kallsyms: Revert back to 128 max symbol length
Sergei Trofimovich (1):
Makefile: enable -Werror=implicit-int and -Werror=strict-prototypes by default
Makefile | 9 +++++++++
scripts/bloat-o-meter | 7 ++++---
scripts/kallsyms.c | 6 ++++++
scripts/mod/sumversion.c | 2 +-
4 files changed, 20 insertions(+), 4 deletions(-)
reply other threads:[~2013-11-15 16:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131115160952.GA19669@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=bp@suse.de \
--cc=fabio.estevam@freescale.com \
--cc=jmario@redhat.com \
--cc=josh@joshtriplett.org \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slyfox@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®