From: Andi Kleen <ak@suse.de>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [patch 2/5] -fstack-protector feature: Add the Kconfig option
Date: Fri, 18 Aug 2006 13:08:07 +0200 [thread overview]
Message-ID: <200608181308.07752.ak@suse.de> (raw)
In-Reply-To: <1155747038.3023.67.camel@laptopd505.fenrus.org>
On Wednesday 16 August 2006 18:50, Arjan van de Ven wrote:
> Subject: [patch 2/5] Add the Kconfig option for the stackprotector feature
> From: Arjan van de Ven <arjan@linux.intel.com>
>
> This patch adds the config options for -fstack-protector.
Normally it's better to add the CONFIG options after the code or
at the same time. Otherwise binary searches later can break
Also can the CC be dropped in the option? It makes it too long.
-Andi
>
next prev parent reply other threads:[~2006-08-18 10:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 16:48 [patch 0/5] -fstack-protector feature for the kernel (try 2) Arjan van de Ven
2006-08-16 16:49 ` [patch 1/5] -fstack-protector feature: annotate the PDA offsets Arjan van de Ven
2006-08-16 16:50 ` [patch 2/5] -fstack-protector feature: Add the Kconfig option Arjan van de Ven
2006-08-16 18:12 ` Adrian Bunk
2006-08-18 11:08 ` Andi Kleen [this message]
2006-08-18 11:23 ` Arjan van de Ven
2006-08-18 14:05 ` Andi Kleen
2006-08-18 13:10 ` Arjan van de Ven
2006-08-18 13:30 ` Arjan van de Ven
2006-08-18 17:21 ` Sam Ravnborg
2006-08-16 16:51 ` [patch 3/5] -fstack-protector feature: Add the canary field to the PDA area Arjan van de Ven
2006-08-16 16:52 ` [patch 4/5] -fstack-protector feature: Add the __stack_chk_fail() function Arjan van de Ven
2006-08-16 16:53 ` [patch 5/5] -fstack-protector feature: Enable the compiler flags in CFLAGS Arjan van de Ven
2006-08-16 18:55 ` Sam Ravnborg
2006-08-16 19:24 ` Arjan van de Ven
2006-08-18 11:15 ` [patch 0/5] -fstack-protector feature for the kernel (try 2) Andi Kleen
2006-08-18 11:29 ` Arjan van de Ven
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=200608181308.07752.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.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