public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Luben Tuikov <ltuikov@yahoo.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	Matthew Wilcox <willy@linux.intel.com>
Subject: Re: [PATCH] [USB] UAS: Achitecture; TMF; more
Date: Sat, 6 Nov 2010 09:34:29 -0700	[thread overview]
Message-ID: <20101106163429.GA5024@kroah.com> (raw)
In-Reply-To: <87456.32791.qm@web31801.mail.mud.yahoo.com>

On Fri, Nov 05, 2010 at 11:52:00PM -0700, Luben Tuikov wrote:
> --- On Fri, 11/5/10, Greg KH <greg@kroah.com> wrote:
> > > This patch changes 86% of the driver. More is to come,
> > but this is
> > > a self-contained patch so it can be applied.
> > 
> > No it can not at all, sorry.
> 
> Greg, would you accept a brand new driver, say uastoo.c (just like
> 8139too.c came about, remember?), or would you say "This is 14% the same
> as uas.c, and thus cannot go in"?

I will say that as you and Mathew need to work together here.

> Did Willy reply to your query about the previous patches? I didn't see
> his reply.

If he did, I did not see his reply either.

I now have a UAS device so I will test your other patches out next week,
and if Matthew is still absent, will have to determine to apply them or
not.

thanks,

greg k-h

  parent reply	other threads:[~2010-11-06 16:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-06  4:46 [PATCH] [USB] UAS: Achitecture; TMF; more Luben Tuikov
2010-11-06  5:14 ` Greg KH
2010-11-06  6:52   ` Luben Tuikov
2010-11-06 10:36     ` Alan Cox
2010-11-06 16:34     ` Greg KH [this message]
2010-11-08 17:36       ` Luben Tuikov
2010-11-08 17:42         ` Greg KH
2010-11-20  1:55 ` Sarah Sharp
2010-12-14  7:58   ` Luben Tuikov
  -- strict thread matches above, loose matches on Subject: below --
2010-12-10 10:52 Luben Tuikov

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=20101106163429.GA5024@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ltuikov@yahoo.com \
    --cc=willy@linux.intel.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