From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: chauplac@gmail.com, dirk@gouders.net, matthijs@stdin.nl,
mmarek@suse.cz, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT] kbuild fixes for v3.10-rc5
Date: Wed, 5 Jun 2013 16:12:06 +0200 [thread overview]
Message-ID: <20130605141206.GA1573@sepie.suse.cz> (raw)
Hi Linus,
There is one fix for a kbuild regression, plus three kconfig fixes for
bugs that have alway been there, but are simple enough to be fixed in an
-rc.
Thanks,
Michal
The following changes since commit f66ba560943ae21f5d1e505bad0a3591823b2b37:
package: Makefile: unbreak binrpm-pkg target (2013-05-16 09:46:45 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git rc-fixes
for you to fetch changes up to 42a0940d9d582214a8d0f8ba41f2b4fe987e21b0:
Merge branch 'yem-kconfig-rc-fixes' of git://gitorious.org/linux-kconfig/linux-kconfig into kbuild/rc-fixes (2013-05-30 15:21:48 +0200)
----------------------------------------------------------------
Clement Chauplannaz (1):
scripts/config: fix assignment of parameters for short version of --*-after options
Dirk Gouders (2):
mconf: handle keys in empty dialogs
kconfig/menu.c: fix multiple references to expressions in menu_add_prop()
Matthijs Kooijman (1):
kbuild: Don't assume dts files live in arch/*/boot/dts
Michal Marek (1):
Merge branch 'yem-kconfig-rc-fixes' of git://gitorious.org/linux-kconfig/linux-kconfig into kbuild/rc-fixes
scripts/Makefile.lib | 2 +-
scripts/config | 2 +-
scripts/kconfig/lxdialog/menubox.c | 9 +++++----
scripts/kconfig/mconf.c | 11 ++++++-----
scripts/kconfig/menu.c | 15 ++++++++++++++-
5 files changed, 27 insertions(+), 12 deletions(-)
reply other threads:[~2013-06-05 14:12 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=20130605141206.GA1573@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=chauplac@gmail.com \
--cc=dirk@gouders.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthijs@stdin.nl \
--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®