public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: bp@alien8.de, dot@dotat.at, mikew@google.com, mmarek@suse.cz,
	randy.dunlap@oracle.com, u.kleine-koenig@pengutronix.de,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT] kbuild core updates for 2.6.39-rc1
Date: Sat, 19 Mar 2011 09:58:02 +0100	[thread overview]
Message-ID: <20110319085802.GA18336@sepie.suse.cz> (raw)

Hi Linus,

please pull these kbuild updates for 2.6.39-rc1:

* Section mismatch analysis enabled by default
  - there are only a few warnings for defconfig builds,
    all{yes,mod}config still has a lot of them. Depending on the general
    perception of this change, we might disable it later in the rc phase
    again.
* Update of unifdef. This is a noop for kbuild, but being in sync
  with upstream is good.
* make W=1 mode that enables a lot of non-default gcc warnings.
* genksyms detects changes in enum constant values.
* two minor fixes.


The following changes since commit c56eb8fb6dccb83d9fe62fd4dc00c834de9bc470:

  Linux 2.6.38-rc1 (2011-01-18 15:14:02 -0800)

are available in the git repository at:
  git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild-2.6.git kbuild

Borislav Petkov (1):
      kbuild: Add extra gcc checks

Michal Marek (8):
      genksyms: Do not paste the bison header file to lex.c
      genksyms: Simplify lexer
      genksyms: Simplify printing of symbol types
      genksyms: Add helpers for building string lists
      genksyms: simplify usage of find_symbol()
      genksyms: Track changes to enum constants
      genksyms: Regenerate lexer and parser
      Merge branch 'genksyms-enum' into kbuild/kbuild

Mike Waychison (1):
      KBuild: silence "'scripts/unifdef' is up to date."

Randy Dunlap (1):
      modpost: fix trailing comma

Tony Finch (1):
      unifdef: update to upstream version 2.5

Uwe Kleine-König (1):
      kbuild: reenable section mismatch analysis

 Documentation/kbuild/kbuild.txt  |    5 +
 Makefile                         |    7 +-
 lib/Kconfig.debug                |    4 -
 scripts/Makefile                 |    5 +
 scripts/Makefile.build           |   35 ++-
 scripts/genksyms/Makefile        |    4 +-
 scripts/genksyms/genksyms.c      |  192 +++++--
 scripts/genksyms/genksyms.h      |    7 +-
 scripts/genksyms/lex.c_shipped   |  427 ++++++----------
 scripts/genksyms/lex.l           |   44 ++-
 scripts/genksyms/parse.c_shipped | 1071 ++++++++++++++++++++++----------------
 scripts/genksyms/parse.h_shipped |   72 +--
 scripts/genksyms/parse.y         |   34 ++-
 scripts/mod/modpost.c            |   23 +-
 scripts/unifdef.c                |  247 +++++++---
 15 files changed, 1237 insertions(+), 940 deletions(-)

             reply	other threads:[~2011-03-19  8:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-19  8:58 Michal Marek [this message]
2011-03-21  0:53 ` [GIT] kbuild core updates for 2.6.39-rc1 Linus Torvalds
2011-03-21  7:47   ` Uwe Kleine-König
2011-03-21 10:17     ` Michal Marek

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=20110319085802.GA18336@sepie.suse.cz \
    --to=mmarek@suse.cz \
    --cc=bp@alien8.de \
    --cc=dot@dotat.at \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikew@google.com \
    --cc=randy.dunlap@oracle.com \
    --cc=torvalds@linux-foundation.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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