From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: dvhart@linux.intel.com, john.stultz@linaro.org,
johnstul@us.ibm.com, lacombar@gmail.com, lizf@cn.fujitsu.com,
pefoley2@verizon.net, udknight@gmail.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT] kconfig for v3.3-rc1
Date: Mon, 16 Jan 2012 21:51:41 +0100 [thread overview]
Message-ID: <20120116205141.GA4691@sepie.suse.cz> (raw)
Hi Linus,
this is the kconfig pull request for v3.3-rc1:
* compiler warning fixes
* new merge_config.sh script that some distributions are using
* menuconfig fix for the exit dialog and a fix for the fix
Michal
The following changes since commit 1ea6b8f48918282bdca0b32a34095504ee65bab5:
Linux 3.2-rc1 (2011-11-07 16:16:02 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git kconfig
Arnaud Lacombe (1):
kbuild: Fix compiler warning with assertion when calling 'fwrite'
Darren Hart (2):
merge_config.sh: use signal names compatible with dash and bash
merge_config.sh: whitespace cleanup
John Stultz (2):
kconfig: add merge_config.sh script
merge_config.sh: fix bug in final check
Li Zefan (1):
menuconfig: fix a regression when canceling the prompt dialog at exit
Peter Foley (4):
kconfig: fix warnings by specifing format arguments
kconfig: fix set but not used warnings
kconfig: use xfwrite wrapper function to silence warnings
Improve update-po-config output
Wang YanQing (1):
menuconfig: let make not report error when not save configuration
scripts/kconfig/Makefile | 6 +-
scripts/kconfig/confdata.c | 4 +-
scripts/kconfig/expr.h | 1 +
scripts/kconfig/gconf.c | 11 +--
scripts/kconfig/lkc.h | 6 +-
scripts/kconfig/mconf.c | 2 +
scripts/kconfig/merge_config.sh | 117 +++++++++++++++++++++++++++++++++++++++
7 files changed, 133 insertions(+), 14 deletions(-)
create mode 100644 scripts/kconfig/merge_config.sh
reply other threads:[~2012-01-16 20:51 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=20120116205141.GA4691@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=dvhart@linux.intel.com \
--cc=john.stultz@linaro.org \
--cc=johnstul@us.ibm.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=pefoley2@verizon.net \
--cc=torvalds@linux-foundation.org \
--cc=udknight@gmail.com \
/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®