All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Andreas Mohr <andi@lisas.de>
Cc: Jeff Garzik <jeff@garzik.org>,
	michal@physics.ubc.ca,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstream-fixes] ata_piix: save, use saved and restore IOCFG
Date: Fri, 02 Jan 2009 17:49:17 +0900	[thread overview]
Message-ID: <495DD50D.7040108@kernel.org> (raw)
In-Reply-To: <20090102082933.GA7881@rhlx01.hs-esslingen.de>

Hello,

Andreas Mohr wrote:
>> This fixes bz#11879.  Andreas Mohr reported and diagnosed the problem.
> 
> I'm mighty unhappy ;-)
> 
> First, I still think prime cause was a weak disk implementation of Word 93
> and not BIOS ACPI handling itself (bug #12202 is a PATA SSD, too!).
> (unless one thinks that BIOS should know about SSD variants of PATA
> and actively do special-case them itself)

Frankly, I don't care one way or the other.  All ->cable_detect() is
supposed to return is the cable type as detected by the controller and
_STM is not supposed to alter the state no matter what.  I don't think
delving into _STM implementation and finding out the exact cause of
flipping cable detection bit leads to the correct solution.  It might
be caused by PATA SSD not setting the cable bit this time but the next
BIOS might as well get it wrong for different reason.  Plus, I don't
see how IDENTIFY data can affect the cable bit unless the ACPI
implementation is snooping IDENTIFY replies.

> Second, you've been keeping silent about the duplicate processing
> for too long (I didn't know about it at all until marked duplicate),
> thus nobody else could derive any hard facts from the doubled information.

My fault but nothing intentional.  When I got the second report, I
couldn't really remember your report other than the fact that I had a
similar report which didn't lead to resolution at the time and between
Christmas and New Year's day, I wasn't paying much attention to bugs
other than following up on each one as comments come up.  ie. I didn't
bother to look up which one was the other one, so the late
association.

> Third, it was not just me who reported it, Carl Michal did >= 10
> reports in his bug.

Are all of those SSD too?

> Fourth, "bz#11879" may seem a precise indication, but when writing
> this within Bugzilla instead of a plain "bug #11879", you probably
> won't have it hyperlinked, thus I'd always prefer the usual
> writing. </nitpick>

Heh... yeah, well.  I've always used OSDL bz#nnnn till now.  Maybe
it's better to use kernel bug#nnnn.

> Patch seems fine to me, thanks a helluva lot for your hard work!
> (probably will test, later)

>> Signed-off-by: Tejun Heo <tj@kernel.org>
> 
> Acked-by: Andreas Mohr <andi@lisas.de>

Thanks.

-- 
tejun

  reply	other threads:[~2009-01-02  8:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02  3:04 [PATCH #upstream-fixes] ata_piix: save, use saved and restore IOCFG Tejun Heo
2009-01-02  8:29 ` Andreas Mohr
2009-01-02  8:49   ` Tejun Heo [this message]
2009-01-02  8:58     ` Andreas Mohr

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=495DD50D.7040108@kernel.org \
    --to=tj@kernel.org \
    --cc=andi@lisas.de \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=michal@physics.ubc.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.