linux-kernel - Re: [PATCHv5 2/3] USB: gadget: Use new composite features in some gadgets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 02 Aug 2010 19:14:08 +0200
From:	Michał Nazarewicz <m.nazarewicz@...sung.com>
To:	Greg KH <greg@...ah.com>
Cc:	David Brownell <david-b@...bell.net>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Dries Van Puymbroeck <Dries.VanPuymbroeck@...imo.com>,
	Kyungmin Park <kyungmin.park@...sung.com>,
	"mina86@...a86.com" <mina86@...a86.com>
Subject: Re: [PATCHv5 2/3] USB: gadget: Use new composite features in some
 gadgets

> On Fri, Jul 30, 2010 at 06:48:41PM +0200, Michał Nazarewicz wrote:
>> So, to fix the situation, I need to ask Greg for the IDs?

On Fri, 30 Jul 2010 18:54:50 +0200, Greg KH <greg@...ah.com> wrote:
> Yes you do.

Could I ask for two IDs then.  One for the Multifunction Composite
Gadget (g_multi) and another for FunctionFS Gadget (g_ffs).  Or is
there some kind of procedure for that?

Again, sorry for all the confusion.  As soon as the gadgets will
get their own IDs I'll repost the patches with fixed IDs and David's
suggestions taken into consideration.

-- 
Best regards,                                        _     _
| Humble Liege of Serenely Enlightened Majesty of  o' \,=./ `o
| Computer Science,  Michał "mina86" Nazarewicz       (o o)
+----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/