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
| ||
|
Date: Thu, 2 May 2013 21:12:42 +0200 From: Arnd Bergmann <arnd@...db.de> To: Alan Stern <stern@...land.harvard.edu> Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, "Greg Kroah-Hartman" <gregkh@...uxfoundation.org> Subject: Re: [PATCH, RFC 16/22] USB: UHCI: clarify Kconfig dependencies On Thursday 02 May 2013, Alan Stern wrote: > On Thu, 2 May 2013, Arnd Bergmann wrote: > > > > What do you think of my patch as compared to yours? > > > > I think in the end it comes down to the question where you want to > > head with your driver. The way I did my version was going towards > > making it similar to EHCI, with stand-alone bus glue drivers > > and a core that is just a library module but does not register > > a device_driver by itself. > > > > Given that there are just three bus glues from UHCI, and at most > > two of them enabled at the same time, I don't see a direct need > > for UHCI to go down the same route as EHCI. If you want to just > > leave this driver alone, your patch is simpler and has the same > > effect in the end. Otherwise I think my patch avoids changing it > > all again once the driver gets reworked. > > Okay then, I'll submit my patch to Greg after the merge window closes. Ok, thanks! Arnd -- 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