From: Greg KH <gregkh@suse.de>
To: Tejun Heo <tj@kernel.org>
Cc: Stefan Lippers-Hollmann <s.L-H@gmx.de>,
linux-kernel@vger.kernel.org, jgarzik@redhat.com,
pchen@nvidia.com, stable@kernel.org
Subject: Re: patch sata_nv-disable-hardreset-for-generic.patch added to 2.6.26-stable tree
Date: Sat, 4 Oct 2008 22:08:16 -0700 [thread overview]
Message-ID: <20081005050816.GA3739@suse.de> (raw)
In-Reply-To: <48E84608.5080108@kernel.org>
On Sun, Oct 05, 2008 at 01:43:52PM +0900, Tejun Heo wrote:
> Greg KH wrote:
> >> It's currently a mess. Please take a look at the following message for
> >> the whole story.
> >>
> >> http://article.gmane.org/gmane.linux.ide/34942
> >>
> >> It's interesting how they fixed hardreset of the chipset step-by-step. :-(
> >
> > Ick, you are right, what a mess.
> >
> > Do you want that patch in 2.6.26-stable now? Or just don't worry about
> > it?
>
> 2.6.26-stable should be fixed but given the series of breakages I
> wanna be a bit cautious before proceeding. Just give me a few more
> days so that I can confirm the posted patch fixes the problem for both
> generic and nf2/3 flavors. I'll forward the final patch against
> -stable to you then.
Sounds good to me.
thanks,
greg k-h
next prev parent reply other threads:[~2008-10-05 5:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081001234424.C72C114543E5@imap.suse.de>
2008-10-04 16:27 ` patch sata_nv-disable-hardreset-for-generic.patch added to 2.6.26-stable tree Stefan Lippers-Hollmann
2008-10-05 2:54 ` Greg KH
2008-10-05 3:20 ` Tejun Heo
2008-10-05 3:48 ` Greg KH
2008-10-05 4:43 ` Tejun Heo
2008-10-05 5:08 ` Greg KH [this message]
2008-10-05 16:00 ` Stefan Lippers-Hollmann
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=20081005050816.GA3739@suse.de \
--to=gregkh@suse.de \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pchen@nvidia.com \
--cc=s.L-H@gmx.de \
--cc=stable@kernel.org \
--cc=tj@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