public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: pdc202xx.c fails to compile in 2.5.15
Date: Mon, 13 May 2002 14:03:56 +0200	[thread overview]
Message-ID: <3CDFABAC.3020802@evision-ventures.com> (raw)
In-Reply-To: <5.1.1.2.2.20020513144903.02885310@mail.lauterbach.com>

Uz.ytkownik Franz Sirl napisa?:
> Alan Cox wrote:
> 
>> > Because of there are apparently devices on which you must check 
>> device class
>> > (2.5.14 talks about CY82C693 and IT8172G), I'll leave proper fix on 
>> Martin,
>> > but simple fix below work fine on my Asus A7V.
>>
>> You need to do specific checks for the device in question. Removing the
>> class check btw is something anyone reading this message should not do
>> even in the same situation unless they know precisely what other
>> mass storage class devices they have present. You can easily trash a
>> raid array otherwise
> 
> 
> I think you are probably talking about the class check for unknown 
> devices a few lines above in 2.5.15. Removing the class check when a 
> driver already claimed responsibility just reinstates what we had in 
> 2.4. The removal is in IDE 61.

Witht the exception that there are not proper vendor id cheks in
2.4 there. Oh well...


  reply	other threads:[~2002-05-13 13:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-13 12:58 pdc202xx.c fails to compile in 2.5.15 Franz Sirl
2002-05-13 12:03 ` Martin Dalecki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-11 16:59 [PATCH] 2.5.15 IDE 60 Martin Dalecki
2002-05-12 19:19 ` pdc202xx.c fails to compile in 2.5.15 Zlatko Calusic
2002-05-12 19:40   ` Jurriaan on Alpha
2002-05-12 22:00   ` Petr Vandrovec
2002-05-13 12:03     ` Alan Cox

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=3CDFABAC.3020802@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.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