From: Michal Marek <mmarek@suse.cz>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kconfig: fix segfault when detecting recursive dependency
Date: Sun, 15 Aug 2010 00:38:23 +0200 [thread overview]
Message-ID: <4C671ADF.6090006@suse.cz> (raw)
In-Reply-To: <20100814124458.GA28387@merkur.ravnborg.org>
Dne 14.8.2010 14:44, Sam Ravnborg napsal(a):
> From 705dbd8a31520722bda78e1bc731e2880f8df0ff Mon Sep 17 00:00:00 2001
> From: Sam Ravnborg <sam@ravnborg.org>
> Date: Sat, 14 Aug 2010 14:40:00 +0200
> Subject: [PATCH] kconfig: fix segfault when detecting recursive dependency
>
> Following sample Kconfig generated a segfault:
>
> config FOO
> bool
> select PERF_EVENTS if HAVE_HW_BREAKPOINT
>
> config PERF_EVENTS
> bool
>
> config HAVE_HW_BREAKPOINT
> bool
> depends on PERF_EVENTS
>
> Fix by reverting back to a valid property if there was no
> property on the stack of symbols.
Applied, thanks.
Michal
prev parent reply other threads:[~2010-08-14 22:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 12:43 [PATCH] Sam Ravnborg
2010-08-14 12:44 ` [PATCH] kconfig: fix segfault when detecting recursive dependency Sam Ravnborg
2010-08-14 22:38 ` Michal Marek [this message]
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=4C671ADF.6090006@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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