From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Brian King <brking@linux.vnet.ibm.com>
Cc: jgarzik@pobox.com, wayneb@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
mbizon@freebox.fr, Tejun Heo <tj@kernel.org>,
Nishanth Aravamudan <nacc@us.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] libata/sas: only set FROZEN flag if new EH is supported
Date: Thu, 23 Jun 2011 15:10:17 +1000 [thread overview]
Message-ID: <1308805817.32158.204.camel@pasglop> (raw)
In-Reply-To: <1308804120.32158.202.camel@pasglop>
On Thu, 2011-06-23 at 14:42 +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2011-06-23 at 14:31 +1000, Benjamin Herrenschmidt wrote:
> > On Tue, 2011-06-21 at 15:30 -0500, Brian King wrote:
> > > Looks good to me. Jeff/Tejun - any issues with merging this?
> >
> > BTW. Current upstream with that patch applied on a machine here leads to
> > several oddities, I don't know at this point whether any of that is
> > actually a regression :
>
> Ooops... pressed "send" too quickly. Here's a log excerpt with some
> comments:
.../...
Ok so most of that is already in 2.6.39, including the odd LUN, so
nothing new under the sun.
I'll do more digging / bisection...
Ben.
next prev parent reply other threads:[~2011-06-23 5:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 19:17 libata/ipr/powerpc: regression between 2.6.39-rc4 and 2.6.39-rc5 Nishanth Aravamudan
2011-06-15 20:02 ` Brian King
2011-06-15 23:34 ` Nishanth Aravamudan
2011-06-16 7:51 ` Tejun Heo
2011-06-16 13:28 ` Brian King
2011-06-16 15:28 ` [PATCH] libata/sas: only set FROZEN flag if new EH is supported Nishanth Aravamudan
2011-06-21 16:07 ` Nishanth Aravamudan
2011-06-21 20:30 ` Brian King
2011-06-21 20:39 ` Jeff Garzik
2011-06-23 4:31 ` Benjamin Herrenschmidt
2011-06-23 4:42 ` Benjamin Herrenschmidt
2011-06-23 5:10 ` Benjamin Herrenschmidt [this message]
2011-06-23 17:15 ` Nishanth Aravamudan
2011-06-23 20:05 ` Brian King
2011-06-23 21:43 ` Benjamin Herrenschmidt
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=1308805817.32158.204.camel@pasglop \
--to=benh@au1.ibm.com \
--cc=brking@linux.vnet.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mbizon@freebox.fr \
--cc=nacc@us.ibm.com \
--cc=tj@kernel.org \
--cc=wayneb@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).