From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Tejun Heo <htejun@gmail.com>,
stable@kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ide: fix drive side 80c cable check, take 2
Date: Wed, 07 Feb 2007 00:09:48 +0100 [thread overview]
Message-ID: <45C90ABC.9060205@gmail.com> (raw)
In-Reply-To: <58cb370e0702061454j1dfe2492w240ca06c028043b7@mail.gmail.com>
Alan wrote:
> On Mon, 5 Feb 2007 21:47:13 +0900
> Tejun Heo <htejun@gmail.com> wrote:
>
>> eighty_ninty_three() had word 93 validitity check but not the 80c bit
>> test itself (bit 12). This increases the chance of incorrect wire
>> detection especially because host side cable detection is often
>> unreliable and we sometimes soley depend on drive side cable
>> detection. Fix it.
>>
>> Signed-off-by: Tejun Heo <htejun@gmail.com>
>> ---
>> Ah... thanks. That explains the code much better. Fixed accordingly.
>>
>> diff --git a/drivers/ide/ide-iops.c b/drivers/ide/ide-iops.c
>> index badde63..6558055 100644
>> --- a/drivers/ide/ide-iops.c
>> +++ b/drivers/ide/ide-iops.c
>> @@ -607,6 +607,8 @@ u8 eighty_ninty_three (ide_drive_t *drive)
>> if(!(drive->id->hw_config & 0x4000))
>> return 0;
>> #endif /* CONFIG_IDEDMA_IVB */
>> + if (!(drive->id->hw_config & 0x2000))
>> + return 0;
>> return 1;
>
> Acked-by: Alan Cox <alan@redhat.com>
applied
next prev parent reply other threads:[~2007-02-06 23:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 7:47 [PATCH] ide: fix drive side 80c cable check Tejun Heo
2007-02-05 11:18 ` Alan
2007-02-05 12:47 ` [PATCH] ide: fix drive side 80c cable check, take 2 Tejun Heo
2007-02-05 13:28 ` Alan
[not found] ` <58cb370e0702061454j1dfe2492w240ca06c028043b7@mail.gmail.com>
2007-02-06 23:09 ` Bartlomiej Zolnierkiewicz [this message]
2007-07-12 18:34 ` Sergei Shtylyov
2007-07-12 18:45 ` Sergei Shtylyov
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=45C90ABC.9060205@gmail.com \
--to=bzolnier@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).