public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Michal Nazarewicz <mina86@mina86.com>
Cc: Klaus Schwarzkopf <schwarzkopf@sensortherm.de>,
	balbi@ti.com, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: add new usb gadget for ACM and mass storage
Date: Fri, 9 Sep 2011 11:43:54 -0700	[thread overview]
Message-ID: <20110909184354.GA30278@suse.de> (raw)
In-Reply-To: <op.v1jdo3g53l0zgt@mnazarewicz-glaptop>

On Fri, Sep 09, 2011 at 12:20:53PM +0200, Michal Nazarewicz wrote:
> >On Thu, Sep 08, 2011 at 08:24:47PM +0200, Klaus Schwarzkopf wrote:
> >>This driver provides two functions in one configuration:
> >>a mass storage, and a CDC ACM (serial port) link.
> >>Heavily based on multi.c and cdc2.c
> 
> On Thu, 08 Sep 2011 21:11:46 +0200, Greg KH <gregkh@suse.de> wrote:
> >I thought the "composite" framework make it so that drivers like this
> >were no longer needed.  Or am I mistaken somehow?
> 
> No.  Composite framework only makes it relatively simple to create such
> gadgets, but one still needs some glue that binds all the functions into
> a single gadget.

Ah, so this is that glue?

> This seems like both a blessing and a curse (which I haven't realise when
> I was creating g_multi) since with n functions implemented one can easily
> came up with 2^n gadgets.

So we can expect more patches like this adding all of the possible
permutations of the different gadget devices?

If so, ick, I thought that the work that was done was to prevent this
from happening, oh well :(

greg k-h

  reply	other threads:[~2011-09-09 18:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 18:24 [PATCH] usb: add new usb gadget for ACM and mass storage Klaus Schwarzkopf
2011-09-08 19:11 ` Greg KH
2011-09-09  8:37   ` Klaus Schwarzkopf
2011-09-09 10:30     ` Michal Nazarewicz
2011-09-09 18:45     ` Greg KH
2011-09-09 10:20   ` Michal Nazarewicz
2011-09-09 18:43     ` Greg KH [this message]
2011-09-16 17:18       ` Sebastian Andrzej Siewior
2011-09-16 17:25         ` Greg KH
2011-09-16 17:30         ` Michal Nazarewicz
2011-09-16 18:22         ` Steve Calfee
2011-09-16 18:55           ` Sebastian Andrzej Siewior
2011-09-16 21:22         ` Alan Stern
2011-10-06 12:08 ` Felipe Balbi
2011-10-07  8:23   ` Klaus Schwarzkopf
2011-10-07  8:38     ` Felipe Balbi
2011-10-07 10:07       ` Klaus Schwarzkopf
2011-10-07 10:14         ` Felipe Balbi
2011-10-07 11:13           ` Sergei Shtylyov
2011-10-07 12:55             ` Felipe Balbi
2011-10-07 11:11     ` Sergei Shtylyov
2011-10-07  8:16 ` [PATCH v2] " Klaus Schwarzkopf
2011-10-07  8:39   ` Felipe Balbi
2011-10-08  7:44 ` [PATCH v3] " Klaus Schwarzkopf
2011-10-10  5:50   ` Felipe Balbi
2011-10-10  8:33     ` Klaus Schwarzkopf
2011-10-10  8:49       ` Felipe Balbi
2011-10-10 10:30         ` Klaus Schwarzkopf
2011-10-10 15:14       ` Alan Stern
2011-10-10 16:00       ` Michal Nazarewicz
2011-10-10  8:32 ` [PATCH v4] " Klaus Schwarzkopf
2011-10-13 17:43   ` Felipe Balbi

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=20110909184354.GA30278@suse.de \
    --to=gregkh@suse.de \
    --cc=balbi@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mina86@mina86.com \
    --cc=schwarzkopf@sensortherm.de \
    /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