linux-kernel - Re: [PATCHv5 1/4] usb: Provide usb_speed

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 for Android: free password hash cracker in your pocket

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

Message-ID: <Pine.LNX.4.44L0.1108261645200.5470-100000@netrider.rowland.org>
Date:	Fri, 26 Aug 2011 16:46:04 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Michal Nazarewicz <mnazarewicz@...gle.com>
cc:	Greg KH <greg@...ah.com>, Felipe Balbi <balbi@...com>,
	Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	Yang Rui Rui <ruirui.r.yang@...to.com>,
	Dave Young <hidave.darkstar@...il.com>,
	<linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCHv5 1/4] usb: Provide usb_speed_string() function

On Fri, 26 Aug 2011, Michal Nazarewicz wrote:

> On Fri, 26 Aug 2011 20:49:05 +0200, Alan Stern <stern@...land.harvard.edu>  
> wrote:
> > I don't know.  Michal, can you look into this?  What we want is:
> >
> > 	common.o gets included in the main kernel if either CONFIG_USB
> > 	or CONFIG_USB_GADGET is set to Y.
> >
> > 	Otherwise, if either symbol is set to M then common.o gets
> > 	built into its own little module.  Perhaps some other stuff
> > 	could get put in there too, though at the moment I can't
> > 	think of anything.
> 
> Wouldn't that be accomplished by a tristate Kconfig option selected by
> USB and USB_GADGET?  Or a tristate that defaults to “y” but depends on
> USB or USB_GADGET?

Like I said, I don't know.  Try it and see.

Alan Stern

--
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/