From: Andrew Morton <akpm@linux-foundation.org>
To: Greg KH <greg@kroah.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
rdunlap@xenotime.net, Achim_Leubner@adaptec.com,
joerg@dorchain.net, stable@kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [stable] [patch 29/29] bug in gdth.c crashing machine
Date: Wed, 7 Mar 2007 11:16:16 -0800 [thread overview]
Message-ID: <20070307111616.16e5e641.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070307174021.GA25066@kroah.com>
On Wed, 7 Mar 2007 09:40:21 -0800 Greg KH <greg@kroah.com> wrote:
> On Wed, Mar 07, 2007 at 11:28:25AM -0600, James Bottomley wrote:
> > On Tue, 2007-03-06 at 02:46 -0800, akpm@linux-foundation.org wrote:
> > > From: Joerg Dorchain <joerg@dorchain.net>
> > >
> > > Undocumented...
> >
> > This is a bit of a problem, isn't it?
> >
> > I have no report of any problem this fixes, and no input from the gdth
> > maintainer about this. The first I actually knew of this patch request
> > is that it appeared in an akpm patch stream yesterday.
> >
> > I really think we need more details before this gets applied to
> > anything, let alone the stable tree.
>
> Randy did forward it to the stable team a while ago too, but I didn't
> know even what tree it applied to as the patch level was a bit off. I
> think he might have some more information about it?
>
Achim did reply: http://lkml.org/lkml/2007/2/23/138
So we don't know what the patch does, but it should be merged into -stable
(and mainline, heaven forfend)
next prev parent reply other threads:[~2007-03-07 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 10:46 [patch 29/29] bug in gdth.c crashing machine akpm
2007-03-07 17:28 ` James Bottomley
2007-03-07 17:40 ` [stable] " Greg KH
2007-03-07 19:16 ` Andrew Morton [this message]
2007-03-07 20:05 ` Joerg Dorchain
2007-03-08 0:50 ` James Bottomley
2007-03-09 18:36 ` Greg KH
2007-03-11 16:03 ` James Bottomley
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=20070307111616.16e5e641.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Achim_Leubner@adaptec.com \
--cc=James.Bottomley@SteelEye.com \
--cc=greg@kroah.com \
--cc=joerg@dorchain.net \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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