From: Greg KH <greg@kroah.com>
To: blaisorblade@yahoo.it
Cc: stable@kernel.org, jdike@addtoit.com, linux-kernel@vger.kernel.org
Subject: Re: [stable] [patch 1/1] uml: quick fix syscall table [urgent]
Date: Fri, 8 Apr 2005 15:06:09 -0700 [thread overview]
Message-ID: <20050408220607.GB3399@kroah.com> (raw)
In-Reply-To: <20050406183802.48AF7C5D4E@zion>
On Wed, Apr 06, 2005 at 08:38:00PM +0200, blaisorblade@yahoo.it wrote:
>
> CC: <stable@kernel.org>
>
> I'm resending this for inclusion in the -stable tree. I've deleted whitespace
> cleanups, and hope this can be merged. I've been asked to split the former
> patch, I don't know if I must split again this one, even because I don't want
> to split this correct patch into multiple non-correct ones by mistake.
Thanks, I've added this to the stable queue.
greg k-h
prev parent reply other threads:[~2005-04-08 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 18:38 [patch 1/1] uml: quick fix syscall table [urgent] blaisorblade
2005-04-06 20:21 ` [stable] " Greg KH
2005-04-07 15:11 ` Blaisorblade
2005-04-08 22:06 ` 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=20050408220607.GB3399@kroah.com \
--to=greg@kroah.com \
--cc=blaisorblade@yahoo.it \
--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