On Mon, Oct 17, 2011 at 03:20:19PM -0700, Greg KH wrote: > On Mon, Oct 10, 2011 at 10:25:07AM -0700, Stephen Warren wrote: > > Marc Dietrich wrote at Sunday, October 09, 2011 9:48 AM: > > > Hi Mikael, > > > > > > thanks for review. The nvec driver received some overhaul in the 3.1 release cycle > > > and he fruids can be viewed in linux-next tree. The nvec client drivers were > > > converted to mfd children in the mean time. This solves the build error, but is not > > > very flexible. We are planing to move the mfd stuct to the board file(s) in the next > > > cycle. > > > > Indeed, the code in v3.1-rc9 is quite different to that in linux-next, so > > this exact problem doesn't exist in linux-next. > > > > However, don't we still want to solve build problems for the final v3.1 > > release, or a stable update to that? As such, > > > > Acked-by: Stephen Warren <swarren@xxxxxxxxxx> > > > > I also CC'd the staging maintainer Greg KH and Tegra maintainers Olof and > > Colin on this email. > > I'm confused, what patch should I apply here? Can someone please resend > it in a format that I can apply it in? With the proper acks? Nevermind, it already was, sorry for the noise... _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
