mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: ltuikov@yahoo.com
Cc: Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] [USB] UASP: USB Attached SCSI (UAS) protocol driver
Date: Fri, 10 Dec 2010 23:42:53 +0000	[thread overview]
Message-ID: <20101210234253.28c5e76e@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <882104.74689.qm@web31813.mail.mud.yahoo.com>

> I think people need to know.

I think they will judge themselves from the full discussion. I'm not sure
they'll vote in your favour however.

"So to expose the obvious, hypothetically, one of the resident "linux
kernel engineers/maintainers" could've submitted AN EMPTY DRIVER that
"binds to" the UAS id, and from then on, any other improvements would
have to go through them"

Strangely that doesn't work because the community isn't full of idiots,
in fact we actively select against them because anyone who is maintaining
a driver needs to be able to deal with other people (at least other
people who wish to be constructive).

"Do you not see HOW DIFFERENT the two drivers are? Do you not see the
difference in quality, presentation, etc, etc."

I find the presentation *very* different. I'm rather worried about the
manner in which it is being presented. Your driver may be the best on the
planet - who knows - but if your response to needing to work with people
is to accuse them of being part of some giant conspiracy or make offensive
comments then that's rapidly going to outweight the quality of the code
and you'll simply run out of people to talk to.

It's actually pretty hard to get in GregKH's kill file, and I suspect by
now you are in a few others as well. So perhaps you can find someone
working with you who has people skills and can sit between you and Greg
and other maintainers and make progress ? It won't be the first time a
user interface problem has been fixed that way in the Linux world.

But basically it's really simple. When we have an existing driver we work
from it - step by step from where we are, to where we want to be. That
series of steps should tell a story so anyone reading the patch series can
understand how it unfolded.

We also have a process for dealing with people not responding, and
irritating them enough they killfile you and refuse to deal with you
isn't that process, especially when you then get yourself killfiled by
the next maintainer up as well.

When you come along late and say "I've got this great other driver", then
sorry you missed the party - you could have submitted yours earlier and
the question becomes "how do I make the existing driver at least as cool
as the one that was too late" not "how do I replace it"

Alan

  reply	other threads:[~2010-12-10 23:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-10 23:15 Luben Tuikov
2010-12-10 23:42 ` Alan Cox [this message]
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
  -- 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-09  0:16 Luben Tuikov
2010-12-09  1:52 ` Greg KH
2010-12-09  2:26   ` Matthew Dharm
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=20101210234253.28c5e76e@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=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

all inboxes | Powered by JetHome®