From: Oliver Neukum <oliver@neukum.org>
To: Rene Rebe <rene@exactcode.de>
Cc: Matthias Kindtner <matthias.kindtner@t-online.de>,
sane-devel <sane-devel@lists.alioth.debian.org>,
linux-kernel@vger.kernel.org
Subject: Re: The never ending hpusbscsi storry
Date: Sat, 5 Mar 2005 08:53:37 +0100 [thread overview]
Message-ID: <200503050853.37226.oliver@neukum.org> (raw)
In-Reply-To: <4228EF0B.7030604@exactcode.de>
Am Samstag, 5. März 2005 00:28 schrieb Rene Rebe:
> Don't ever use hpusbscsi. I though I already told all vedors it is that
> broken that they should never ever ship it. It is the first thing that
> will be removed in Linux 2.7.
>
> If it would be me it would be removed from _all kernels right now_ ...
It shall be. A patch to do that is in the queue. The other users have
gone away.
Regards
Oliver
prev parent reply other threads:[~2005-03-05 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200503050010.04190.matthias.kindtner@t-online.de>
2005-03-04 23:28 ` The never ending hpusbscsi storry Rene Rebe
2005-03-05 7:53 ` Oliver Neukum [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=200503050853.37226.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.kindtner@t-online.de \
--cc=rene@exactcode.de \
--cc=sane-devel@lists.alioth.debian.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).