From: Sam Ravnborg <sam@ravnborg.org>
To: linux-kbuild <linux-kbuild@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: pending kbuild updates
Date: Mon, 29 Dec 2008 14:44:02 +0100 [thread overview]
Message-ID: <20081229134402.GA7069@uranus.ravnborg.org> (raw)
Following is the next batch queued up for merging.
Highlights:
o improved userspace header checks (spawns a lot of warnings now!)
o some kconfig improvements for check of recursive dependencies
o drop retrun of void warning from sparse
Sam
Hannes Eder (1):
kbuild: disable sparse warning "returning void-valued expression"
Mike Frysinger (2):
headers_check.pl: disallow extern's
kbuild: in headers_install autoconvert asm/inline/volatile to __xxx__
Randy Dunlap (1):
kbuild: make *config usage docs
Sam Ravnborg (9):
m68k: fix recursive dependency in Kconfig
kconfig: explain symbol value defaults
kconfig: add comments to symbol flags
kconfig: struct property commented
kconfig: improve readout when we hit recursive dependencies
kconfig: print all locations when we see a recursive dependency
kconfig: improve error messages for bad source statements
kbuild: check for leaked CONFIG_ symbols to userspace
kbuild: document environment variables
Documentation/kbuild/00-INDEX | 6 +-
Documentation/kbuild/kbuild.txt | 126 +++++++++++++++++++++++
Documentation/kbuild/kconfig.txt | 188 +++++++++++++++++++++++++++++++++++
Makefile | 3 +-
README | 32 ++++---
arch/m68k/Kconfig | 1 -
scripts/headers_check.pl | 21 ++++-
scripts/headers_install.pl | 3 +
scripts/kconfig/expr.h | 83 ++++++++++-----
scripts/kconfig/lex.zconf.c_shipped | 7 +-
scripts/kconfig/menu.c | 2 +
scripts/kconfig/symbol.c | 27 ++++-
scripts/kconfig/zconf.l | 7 +-
13 files changed, 453 insertions(+), 53 deletions(-)
next reply other threads:[~2008-12-29 13:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 13:44 Sam Ravnborg [this message]
2008-12-29 13:53 ` [PATCH 01/13] m68k: fix recursive dependency in Kconfig Sam Ravnborg
2008-12-29 13:53 ` [PATCH 02/13] kconfig: explain symbol value defaults Sam Ravnborg
2008-12-29 13:53 ` [PATCH 03/13] kconfig: add comments to symbol flags Sam Ravnborg
2008-12-29 13:53 ` [PATCH 04/13] kconfig: struct property commented Sam Ravnborg
2008-12-29 13:53 ` [PATCH 05/13] kconfig: improve readout when we hit recursive dependencies Sam Ravnborg
2008-12-29 13:53 ` [PATCH 06/13] kconfig: print all locations when we see a recursive dependency Sam Ravnborg
2008-12-31 2:55 ` Roman Zippel
2008-12-31 9:05 ` Sam Ravnborg
2009-01-18 20:54 ` Sam Ravnborg
2008-12-29 13:53 ` [PATCH 07/13] kconfig: improve error messages for bad source statements Sam Ravnborg
2008-12-29 13:53 ` [PATCH 08/13] headers_check.pl: disallow extern's Sam Ravnborg
2008-12-29 13:53 ` [PATCH 09/13] kbuild: check for leaked CONFIG_ symbols to userspace Sam Ravnborg
2008-12-29 13:53 ` [PATCH 10/13] kbuild: in headers_install autoconvert asm/inline/volatile to __xxx__ Sam Ravnborg
2008-12-29 13:53 ` [PATCH 11/13] kbuild: disable sparse warning "returning void-valued expression" Sam Ravnborg
2008-12-29 13:53 ` [PATCH 12/13] kbuild: make *config usage docs Sam Ravnborg
2008-12-29 13:53 ` [PATCH 13/13] kbuild: document environment variables Sam Ravnborg
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=20081229134402.GA7069@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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