From: Michal Marek <mmarek@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kyle@redhat.com, lacombar@gmail.com, mmarek@suse.cz,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT] kconfig rc fixes
Date: Sun, 10 Oct 2010 00:40:41 +0200 [thread overview]
Message-ID: <20101009224041.GA901@sepie.suse.cz> (raw)
Hi Linus,
I have three fixes that should ideally go into 2.6.36:
1) Kyle's make oldnoconfig fix: make oldnoconfig was added and later got
broken, all in 2.6.36-rc1.
2) Arnaud's fix for a crash in kconfig caused by a use-after-free bug.
This fix has the unfortunate side effect that most configurations
(e.g. make defconfig on x86) start printing warnings several lines
long. These warnings are valid, but were not detected before. To
avoid receiving tens of reports about this once 2.6.36 is out, I
decided to comment out the warnings completely for the final release,
as there is not enough time to fix the root causes.
Please consider for 2.6.36. Or if you are only willing to take either 1)
or 2), let me know and I'll prepare such branch.
Thanks,
Michal
The following changes since commit cb655d0f3d57c23db51b981648e452988c0223f9:
Linux 2.6.36-rc7 (2010-10-06 13:39:52 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild-2.6.git rc-fixes
Arnaud Lacombe (1):
kconfig: delay symbol direct dependency initialization
Kyle McMartin (1):
kbuild: fix oldnoconfig to do the right thing
Michal Marek (1):
kconfig: Temporarily disable dependency warnings
scripts/kconfig/conf.c | 2 +-
scripts/kconfig/expr.h | 1 -
scripts/kconfig/menu.c | 7 ++-----
scripts/kconfig/symbol.c | 2 ++
4 files changed, 5 insertions(+), 7 deletions(-)
next reply other threads:[~2010-10-09 22:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 22:40 Michal Marek [this message]
2010-11-03 22:29 ` REGRESSION: Re: [GIT] kconfig rc fixes Mauro Carvalho Chehab
2010-11-03 22:47 ` Michal Marek
2010-11-03 23:02 ` Mauro Carvalho Chehab
2010-11-04 2:31 ` Arnaud Lacombe
2010-11-04 3:19 ` Mauro Carvalho Chehab
2010-11-04 4:02 ` Arnaud Lacombe
2010-11-04 4:15 ` Arnaud Lacombe
2010-11-04 11:10 ` Mauro Carvalho Chehab
2010-11-04 17:19 ` Randy Dunlap
2010-11-04 18:11 ` Mauro Carvalho Chehab
2010-11-04 18:32 ` Arnaud Lacombe
2010-11-04 18:51 ` Mauro Carvalho Chehab
2010-11-05 12:02 ` Jean Delvare
2010-11-04 18:34 ` Arnaud Lacombe
2010-11-04 18:43 ` Mauro Carvalho Chehab
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=20101009224041.GA901@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=kyle@redhat.com \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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