public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Jones <davej@redhat.com>,
	linux-kernel@vger.kernel.org, sam@ravnborg.org,
	arjan@infradead.org, gregkh@suse.de, stable@kernel.org,
	stable-commits@vger.kernel.org
Subject: Re: [stable] patch kbuild-allow-fstack-protector-to-take-effect.patch added to 2.6.24-stable tree
Date: Fri, 22 Feb 2008 15:18:08 -0800	[thread overview]
Message-ID: <20080222231808.GA30669@kroah.com> (raw)
In-Reply-To: <20080222230604.GA20829@redhat.com>

On Fri, Feb 22, 2008 at 06:06:04PM -0500, Dave Jones wrote:
> On Fri, Feb 22, 2008 at 03:00:58PM -0800, gregkh@suse.de wrote:
>  > 
>  > This is a note to let you know that we have just queued up the patch titled
>  > 
>  >      Subject: kbuild: allow -fstack-protector to take effect
>  > 
>  > to the 2.6.24-stable tree.  Its filename is
>  > 
>  >      kbuild-allow-fstack-protector-to-take-effect.patch
>  > 
>  > A git repo of this tree can be found at 
>  >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> 
> Is this wise given this thread..  http://lkml.org/lkml/2008/2/22/101    ?
> 
> At least until the problem is understood, not enabling this seems like
> a better option for -stable

I thought that thread was for the much larger patches, not just this
Makefile change.

Or am I wrong here?  If so, I'll gladly drop it.  Arjan?  Sam?

thanks,

greg k-h

  reply	other threads:[~2008-02-22 23:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200802190005.m1J05SKP017015@hera.kernel.org>
     [not found] ` <20080222230103.CC4EF14540D0@imap.suse.de>
2008-02-22 23:06   ` patch kbuild-allow-fstack-protector-to-take-effect.patch added to 2.6.24-stable tree Dave Jones
2008-02-22 23:18     ` Greg KH [this message]
2008-02-22 23:34       ` [stable] " Dave Jones
2008-02-22 23:42         ` Greg KH
2008-02-22 23:59           ` Dave Jones
2008-02-23  1:08             ` Greg KH

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=20080222231808.GA30669@kroah.com \
    --to=greg@kroah.com \
    --cc=arjan@infradead.org \
    --cc=davej@redhat.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@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