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
| ||
|
Message-ID: <20130111181331.GM14149@atomide.com> Date: Fri, 11 Jan 2013 10:13:32 -0800 From: Tony Lindgren <tony@...mide.com> To: Roger Quadros <rogerq@...com> Cc: balbi@...com, gregkh@...uxfoundation.org, sameo@...ux.intel.com, kishon@...com, linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCH 01/14] mfd: omap-usb-host: Consolidate OMAP USB-HS platform data * Roger Quadros <rogerq@...com> [130111 01:43]: > Tony, > > On 01/11/2013 01:45 AM, Tony Lindgren wrote: > > * Roger Quadros <rogerq@...com> [130110 08:54]: > >> Let's have a single platform data structure for the OMAP's High-Speed > >> USB host subsystem instead of having 3 separate ones i.e. one for > >> board data, one for USB Host (UHH) module and one for USB-TLL module. > >> > >> This makes the code much simpler and avoids creating multiple copies of > >> platform data. > > > > I can apply just this patch alone into an immutable branch that > > we all can merge in as needed as long as we have acks for the USB > > and MFD parts. > > > > Or does this one need to be changed based on Alan's comments > > on the EHCI lib related changes? > > > > This does not depend on EHCI lib based changes but it depends on the > OMAP USB Host cleanup series posted earlier. Can we first apply just the minimal platform_data + board file + clock changes? That way I can apply those to some immutable tree for everybody to use, and we cut off the dependency to the driver changes for the rest of the patches. And then I'm off the hook for the rest of the patches :) Tony -- 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/
Powered by blists - more mailing lists