From: Greg KH <greg@kroah.com>
To: Luben Tuikov <ltuikov@yahoo.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] [USB] UASP: USB Attached SCSI (UAS) protocol driver
Date: Wed, 8 Dec 2010 17:52:04 -0800 [thread overview]
Message-ID: <20101209015204.GA8339@kroah.com> (raw)
In-Reply-To: <233716.61101.qm@web31813.mail.mud.yahoo.com>
On Wed, Dec 08, 2010 at 04:16:06PM -0800, Luben Tuikov wrote:
> --- On Mon, 12/6/10, Greg KH <greg@kroah.com> wrote:
> >
> > We already have this support in the kernel tree,
>
> Greg, this isn't an effort for "linux kernel code turf". This is a
> well-implemented driver according to the respective specifications
> (SAM, SPC, USB 2/3). It reflects correct implementation, naming, etc.
> It shows understanding of the abstraction layers and underlying
> technology. It's what you'd want to have in /YOUR/ kernel.
What I don't want in _anyones_ kernel is multiple drivers wanting to
attach to the same device.
> > why do you want and need another driver that does the same exact thing?
>
> Nothing can be further from the truth. The current uas.c driver
> doesn't do the "exact same thing", far from it.
>
> You responded 4 minutes after my post. Did you have to time to verify
> that the driver I posted does "the exact same thing" as the one in the
> kernel?
By "same thing" I mean "binds to the same device."
I have lived through the hell of this in the past and I will not let
that happen again, sorry.
>
> "The exact same thing", let's see:
<snip>
I'm not saying that the in-kernel driver is perfect at all, and it's
author is getting annoying by refusing to answer my emails, but still,
please work with him to get the in-kernel driver to work up to your
needs.
If you have problems with the maintainer, please let me know and I'll
see what I can do.
But again, this driver is not acceptable as-is, sorry.
thanks,
greg k-h
next prev parent reply other threads:[~2010-12-09 1:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 0:16 [PATCH] [USB] UASP: USB Attached SCSI (UAS) protocol driver Luben Tuikov
2010-12-09 1:52 ` Greg KH [this message]
2010-12-09 2:26 ` Matthew Dharm
-- strict thread matches above, loose matches on Subject: below --
2010-12-14 17:25 Luben Tuikov
2010-12-14 18:12 ` Ben Gamari
2010-12-15 22:17 ` Luben Tuikov
2010-12-16 6:29 ` Andreas Mohr
2010-12-16 9:46 ` Luben Tuikov
2010-12-16 12:11 ` Andreas Mohr
2010-12-13 21:46 Luben Tuikov
2010-12-13 22:37 ` Matthew Dharm
2010-12-10 23:15 Luben Tuikov
2010-12-10 23:42 ` Alan Cox
2010-12-11 2:26 ` Luben Tuikov
2010-12-13 18:40 ` Mark Brown
2010-12-13 19:48 ` Matthias Schniedermeyer
2010-12-13 21:53 ` Luben Tuikov
2010-12-13 21:53 ` Andreas Mohr
2010-12-14 0:42 ` Sarah Sharp
2010-12-14 8:30 ` Luben Tuikov
2010-12-13 21:34 ` Luben Tuikov
2010-12-06 17:05 Luben Tuikov
2010-12-06 17:09 ` Greg KH
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=20101209015204.GA8339@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ltuikov@yahoo.com \
/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