Hi

On Sonntag, 5. Oktober 2008, Greg KH wrote:
quoted text
> On Sat, Oct 04, 2008 at 06:27:03PM +0200, Stefan Lippers-Hollmann wrote:
> > Hi
> >=20
> > On Donnerstag, 2. Oktober 2008, gregkh@suse.de wrote:
> > >=20
> > > This is a note to let you know that we have just queued up the patch =
titled
quoted text
> > >=20
> > >     Subject: sata_nv: disable hardreset for generic
> > >=20
> > > to the 2.6.26-stable tree.  Its filename is
> > >=20
> > >     sata_nv-disable-hardreset-for-generic.patch
> > >=20
> > > A git repo of this tree can be found at=20
> > >     http://www.kernel.org/git/?p=3Dlinux/kernel/git/stable/stable-que=
ue.git;a=3Dsummary
quoted text
> > >=20
> > >=20
> > > From 2fd673ecf0378ddeeeb87b3605e50212e0c0ddc6 Mon Sep 17 00:00:00 2001
> > > From: Tejun Heo <tj@kernel.org>
> > > Date: Fri, 29 Aug 2008 16:13:12 +0200
> > > Subject: sata_nv: disable hardreset for generic
> > >=20
> > > From: Tejun Heo <tj@kernel.org>
> > >=20
> > > commit 2fd673ecf0378ddeeeb87b3605e50212e0c0ddc6 upstream
> > >=20
> > > of them being unifying probing, hotplug and EH reset paths uniform.
> > > Previously, broken hardreset could go unnoticed as it wasn't used
> > > during probing but when something goes wrong or after hotplug the
> > > problem will surface and bite hard.
> > >=20
> > > OSDL bug 11195 reports that sata_nv generic flavor falls into this
> > > category.  Hardreset itself succeeds but PHY stays offline after
> > > hardreset.  I tried longer debounce timing but the result was the
> > > same.
> > >=20
> > >   http://bugzilla.kernel.org/show_bug.cgi?id=3D11195
> > >=20
> > > So, it seems we'll have to drop hardreset from the generic flavor.
> > >=20
> > > Signed-off-by: Tejun Heo <tj@kernel.org>
> > > Cc: Peer Chen <pchen@nvidia.com>
> > > Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> >=20
> > On 2.6.26.5 + the pending stable queue applied, this patch results in l=
ots=20
quoted text
> > of noise in my syslog (full gzipped dmesg with and without this patch=20
> > attached):
>=20
> This patch has been removed from the stable queue, so it shouldn't be an
> issue anymore, right?

Yes, you're right. I missed it being removed from queue-2.6.26 a few hours=
=20
before I actually sent the mail, sorry for the noise.

Thanks
	Stefan Lippers-Hollmann