From: Jean Delvare <jdelvare@suse.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH] CONFIG_CC_STACKPROTECTOR is no longer experimental
Date: Fri, 06 Jul 2012 19:57:19 +0200 [thread overview]
Message-ID: <1341597439.4655.23.camel@amber.site> (raw)
In-Reply-To: <4FF71F1C.4040608@xenotime.net>
Hi Randy,
Le vendredi 06 juillet 2012 à 10:23 -0700, Randy Dunlap a écrit :
> On 07/06/2012 07:08 AM, Jean Delvare wrote:
>
> > This feature has been around for over 5 years now, so I presume it is
> > no longer considered experimental.
> >
> > Signed-off-by: Jean Delvare <jdelvare@suse.de>
> > Cc: Ingo Molnar <mingo@redhat.com>
> > Cc: Arjan van de Ven <arjan@linux.intel.com>
> > Cc: Andi Kleen <andi@firstfloor.org>
> > ---
> > Or is there any reason to still consider this an experimental feature?
>
>
> I doubt it, but if it is still experimental, it should also have
> depends on EXPERIMENTAL
Agreed.
> and then it would be nice if kconfig (the software) would add the
> " (EXPERIMENTAL)" tag when it sees such a dependency.
Oh yeah, I've been dreaming of this for years now but never found the
time to actually look into implementing it. Not sure if I would actually
be able to anyway, as it will probably require some Kconfig magic beyond
my knowledge.
--
Jean Delvare
Suse L3
next prev parent reply other threads:[~2012-07-06 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 14:08 Jean Delvare
2012-07-06 17:23 ` Randy Dunlap
2012-07-06 17:57 ` Jean Delvare [this message]
2012-07-06 17:58 ` Arjan van de Ven
2012-07-06 20:19 ` Paul Bolle
2012-07-09 7:56 ` Jean Delvare
2012-07-09 11:50 ` Jean Delvare
2012-07-09 13:11 ` Arjan van de Ven
2012-07-09 12:08 ` [tip:x86/urgent] x86: CONFIG_CC_STACKPROTECTOR= y " tip-bot for Jean Delvare
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=1341597439.4655.23.camel@amber.site \
--to=jdelvare@suse.de \
--cc=andi@firstfloor.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@xenotime.net \
/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®