On Sun, May 15, 2011 at 12:20:51PM +0200, Linus Walleij wrote: > 2011/5/10 Par-Gunnar Hjalmdahl <par-gunnar.p.hjalmdahl@xxxxxxxxxxxxxx>: > > > Patch created on next-20110510. > > Compared to v5 this patch has the following update: > > - Updated driver after changes to MFD interfaces in linux-next (from mfd_data > > to platform_data). > > - Changed platform specific file dependencies (included correct nomadik file). > > Sorry I don't know if all this will work, it's due to all the churn created by > the current push to get stuff out of the ARM tree so not much to do. > > The Nomadik GPIO file was moved in next but I will take that code move > out today, because the GPIO maintainer has told me he couldn't > provide feedback on these patches in time for me to finalize the change > for kernel 2.6.40. Thus it won't go into 2.6.40 and I must remove it > from next. > > The MFD changes will *probably* happen, if you're thinking about the > PRCMU movement etc. > > To merge into the staging tree right now, you need to base it off > Gregs staging tree, which is where it'll be merged: > http://git.kernel.org/?p=linux/kernel/git/gregkh/staging-2.6.git;a=summary > > Sorry about all the confusion, I think it's actually nobodys fault, > it's just reflecting the fact that embedded drivers with deep > platform dependencies are *really* *hard* to manage in staging. That's why you should only use staging as a last resort, not as your primary way of getting code into the kernel, especially for stuff with a constantly changing in-kernel interface like you have pointed out here. Just do the "real work" first and get it merged the real way if at all possible. best of luck, greg k-h _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
