public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <ltuikov@yahoo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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: Mon, 13 Dec 2010 13:46:58 -0800 (PST)	[thread overview]
Message-ID: <72920.27902.qm@web31804.mail.mud.yahoo.com> (raw)

--- On Sat, 12/11/10, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> 
> > Alan, don't you work for the same company as do the
> authors listed in "uas.c"?
> 
> If you've got nothing better to do than insinuate further
> unpleasant
> things when people try and help then don't expect any help
> from anyone.
> 
> *plonk*

Alan,

When in doubt, follow the money.

The problem isn't in that you're trying to do what is convenient for the corporation which has hired you and pays your salary. The problem is that you're still pretending that you have the interests of _free_ open source *as you once had*.

Did you review my driver? Did anyone else in this thread? No, of course not. You didn't even do it the second time I called your bluff in this thread. Why not? Simple, it's not what you're getting paid to do now.

Can you imagine Greg pulling out a defunct driver written by a co-worker of yours, (working for the same large corporation as you are), in favor of some no-name working driver? I mean imagine the sponsorships, the free equipment, etc your company provides to you, Greg and the "Linux community"? Your company is the single largest sponsor of Linux conferences and anything Linux. 

After all, who do you think got Greg a UAS device?  (not me ;-) )

    Luben


             reply	other threads:[~2010-12-13 21:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13 21:46 Luben Tuikov [this message]
2010-12-13 22:37 ` [PATCH] [USB] UASP: USB Attached SCSI (UAS) protocol driver 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-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-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=72920.27902.qm@web31804.mail.mud.yahoo.com \
    --to=ltuikov@yahoo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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