From: Greg KH <greg@kroah.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: gregkh@suse.de, LKML <linux-kernel@vger.kernel.org>,
akpm@osdl.org, jdike@addtoit.com, ak@suse.de, stable@kernel.org
Subject: Re: [stable] patch x86_64-fix-2.6.18-regression-ptrace_oldsetoptions-should-be-accepted.patch queued to -stable tree
Date: Wed, 21 Feb 2007 16:32:25 -0800 [thread overview]
Message-ID: <20070222003225.GC30480@kroah.com> (raw)
In-Reply-To: <200702211343.43112.blaisorblade@yahoo.it>
On Wed, Feb 21, 2007 at 01:43:42PM +0100, Blaisorblade wrote:
> On Wednesday 21 February 2007 00:41, gregkh@suse.de wrote:
> > This is a note to let you know that we have just queued up the patch titled
> >
> > Subject: x86_64: fix 2.6.18 regression - PTRACE_OLDSETOPTIONS should
> > be accepted
> >
> > to the 2.6.18-stable tree. Its filename is
>
> Since you are still maintaining 2.6.18, I've just sent another patch for that,
> i.e. the backport of commit 14679eb3c50897889ba62f9a37e3bcd8a205b5e7.
> Could you still merge it in this release, especially since this is the last
> 2.6.18-stable you are doing?
> Also, this patch should also be merged in 2.6.20, but I saw no mail about
> this, so I wanted to make sure it's heading there too.
>
> > x86_64-fix-2.6.18-regression-ptrace_oldsetoptions-should-be-accepted.patch
> >
> > A git repo of this tree can be found at
> >
> > http://www.kernel.org/git/?p=linux/kernel/git/gregkh/stable-queue.git;a=sum
> >mary
>
> Hmm, this should be (note the missing gregkh in the path):
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
Ah, good point, I'll go change my script that generates this, thanks for
pointing it out.
greg k-h
prev parent reply other threads:[~2007-02-22 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070220234253.7B612C15B05@imap.suse.de>
2007-02-21 12:43 ` Blaisorblade
2007-02-22 0:29 ` [stable] " Greg KH
2007-02-22 0:32 ` Greg KH [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=20070222003225.GC30480@kroah.com \
--to=greg@kroah.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=blaisorblade@yahoo.it \
--cc=gregkh@suse.de \
--cc=jdike@addtoit.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®