linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
	Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH #upstream-fixes] libata-acpi: missing _SDD is not an error
Date: Fri, 20 Nov 2009 17:58:38 +0900	[thread overview]
Message-ID: <4B065A3E.3040404@kernel.org> (raw)
In-Reply-To: <4B0657D6.3000004@garzik.org>

Hello,

11/20/2009 05:48 PM, Jeff Garzik wrote:
> On 11/18/2009 08:24 AM, Tejun Heo wrote:
>> Missing _SDD is not an error.  Don't treat it as one.
>>
>> Signed-off-by: Tejun Heo<tj@kernel.org>
>> Reported-by: Takashi Iwai<tiwai@suse.de>
>> ---
>>   drivers/ata/libata-acpi.c |   15 +++++++++------
>>   1 file changed, 9 insertions(+), 6 deletions(-)
> 
> 
> hmmmm, do you have a link to the bug report?

Unfortunately, it's from novell internal bugzilla entry, but the
following is how it looks like without the patch.

[   15.720046] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   16.540846] ata1.00: ACPI _SDD failed (AE 0x5)
[   16.553907] ata1.00: ACPI: failed the second time, disabled
[   16.567311] ata1.00: configured for UDMA/100

> How critical is this?  Is it a regression fix?

It's not critical.  libata-acpi code will give up after a couple of
tries and just turn off ACPI and is not a regression.

> We are very late into 2.6.32-rc, where we try to minimize the patches
> applied as much as possible.

This can go into #upstream then.  No biggie.

Thanks.

-- 
tejun

      parent reply	other threads:[~2009-11-20  8:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 13:24 [PATCH #upstream-fixes] libata-acpi: missing _SDD is not an error Tejun Heo
2009-11-19 23:36 ` Jeff Garzik
2009-11-20  8:48 ` Jeff Garzik
2009-11-20  8:56   ` Takashi Iwai
2009-11-20  8:58     ` Jeff Garzik
2009-11-20  8:58   ` Tejun Heo [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=4B065A3E.3040404@kernel.org \
    --to=tj@kernel.org \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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).