public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: "O.Sezer" <sezeroz@ttnet.net.tr>
Cc: linux-kernel@vger.kernel.org, marcelo.tosatti@cyclades.com,
	zaitcev@redhat.com
Subject: Re: [PATCH 2.4] blacklist a device in usb-storage
Date: Mon, 16 Aug 2004 08:07:51 -0700	[thread overview]
Message-ID: <20040816080751.733c188d@lembas.zaitcev.lan> (raw)
In-Reply-To: <412066BC.9040503@ttnet.net.tr>

On Mon, 16 Aug 2004 10:48:12 +0300
"O.Sezer" <sezeroz@ttnet.net.tr> wrote:

> > I do not understand what the objective might be. Just do not
> > use that thing with Linux kernel 2.4. Why do you wish "to revent
> > usb-storage from taking over this disk"?

> As I said above, I cannot prevent accidentals (VID/PIDs aren't
> printed on the disk, yo know...) And usb-storage must not deal
> with disks that it cannot deal with:
> 1. This particular disk can lead to panics as I said.
> 2. If someone ever writes a driver specific to this device (I
>     know it's less than highly unlikely), than it would be also
>     useful in that case if the disk isn't tried to be owned by
>     usb-storage. That, I think applies as a general case, too.

The #2 only makes sense when such driver appears.

As for #1, why don't you post the dmesg from your "panic".

-- Pete

  reply	other threads:[~2004-08-16 15:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1092508141.32379.linux-kernel2news@redhat.com>
2004-08-16  6:52 ` [PATCH 2.4] blacklist a device in usb-storage Pete Zaitcev
2004-08-16  7:48   ` O.Sezer
2004-08-16 15:07     ` Pete Zaitcev [this message]
2004-08-16 15:54       ` O.Sezer
2004-08-16 22:32         ` Pete Zaitcev
2004-08-17 11:12           ` O.Sezer
2004-08-16 16:12       ` O.Sezer
2004-08-14 18:22 O.Sezer

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=20040816080751.733c188d@lembas.zaitcev.lan \
    --to=zaitcev@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=sezeroz@ttnet.net.tr \
    /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