From: Greg KH <gregkh@suse.de>
To: merez@codeaurora.org
Cc: Greg KH <greg@kroah.com>,
linux-usb@vger.kernel.org, linux-arm-msm@vger.kernel.org,
David Brownell <dbrownell@users.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH v2] usb: Add streams support to epautoconf.
Date: Tue, 21 Dec 2010 09:58:27 -0800 [thread overview]
Message-ID: <20101221175827.GA8709@suse.de> (raw)
In-Reply-To: <ccc3842ee0be7b1036143d1fccd005a0.squirrel@www.codeaurora.org>
On Tue, Dec 21, 2010 at 05:46:34AM -0800, merez@codeaurora.org wrote:
> > On Mon, Dec 20, 2010 at 11:58AM, Greg KH wrote:
> > Ok, but please note the word of "proprietary" usually means something
> else when talking about kernel code (i.e. licensing issues.)
> >
> > I'll be glad to take this type of patch when you also provide a patch
> that uses the callback, but not before then.
>
> What I meant by "proprietary" is not proprietary in the terms of kernel
> world. I meant a unique algorithm, different from the default. Sorry for
> the misunderstanding.
> Currently we don't have a unique algorithm. When implementing this change
> we thought it may be useful for other controllers but for us the default
> implementation was good enough.
First rule of kernel development, "don't add infrastructure that you do
not need today."
thanks,
greg k-h
next prev parent reply other threads:[~2010-12-21 17:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 13:46 [RFC/PATCH v2] usb: Add streams support to epautoconf merez
2010-12-21 17:58 ` Greg KH [this message]
2010-12-22 11:58 ` merez
2010-12-28 7:23 ` merez
-- strict thread matches above, loose matches on Subject: below --
2010-12-20 19:33 merez
2010-12-20 19:58 ` Greg KH
2010-12-16 7:34 Maya Erez
2010-12-16 18:15 ` 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=20101221175827.GA8709@suse.de \
--to=gregkh@suse.de \
--cc=dbrownell@users.sourceforge.net \
--cc=greg@kroah.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=merez@codeaurora.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).