Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751432AbWCQQuT (ORCPT ); Fri, 17 Mar 2006 11:50:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751480AbWCQQuS (ORCPT ); Fri, 17 Mar 2006 11:50:18 -0500 Received: from zproxy.gmail.com ([64.233.162.207]:60886 "EHLO zproxy.gmail.com") by vger.kernel.org with ESMTP id S1751432AbWCQQuQ convert rfc822-to-8bit (ORCPT ); Fri, 17 Mar 2006 11:50:16 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=R4GJtb82r/EPLbmMGoL9gdMvC6hyeBhjI6EBF+DBX6ZR1ATB8Ukd/3xP33tuL4da4emAuFJknNsmtPvsvbNyv+fVa4fI4CVe/rlG3QJEMlfojm2J4/xG3Jg369SAAVPn/Zy4wVOxX6u1q+uLetUSwDNG5O6+fLYQ5u88lTurGpw= Message-ID: <6bffcb0e0603170850i5f955151v@mail.gmail.com> Date: Fri, 17 Mar 2006 17:50:15 +0100 From: "Michal Piotrowski" To: "Arjan van de Ven" Subject: Re: [Patch 0/8] Port of -fstack-protector to the kernel Cc: linux-kernel@vger.kernel.org In-Reply-To: <1142611850.3033.100.camel@laptopd505.fenrus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Content-Disposition: inline References: <1142611850.3033.100.camel@laptopd505.fenrus.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 671 Lines: 22 Hi, On 17/03/06, Arjan van de Ven wrote: > This patch series adds support for the gcc 4.1 -fstack-protector feature to > the kernel. Unfortunately this needs a gcc patch before it can work, so at > this point these patches are just for comment, not for merging. > It's x86_64 specific? Regards, Michal -- Michal K. K. Piotrowski LTG - Linux Testers Group (http://www.stardust.webpages.pl/ltg/wiki/) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/