Hi Aaron, On Wed, Jul 18 2012, Aaron Lu wrote: > Is the following patch OK? This is based on top of current mmc-next with > the previous one in tree. Not sure if this is what you want though. Yes, that's perfect; squashed into the original patch and pushed out to mmc-next. Thanks! Having there be so many MAX_CURRENT defines -- and having them be split in the middle between CAP_ and CAP2_ -- is starting to feel a bit awkward. Does anyone have ideas on how that might be tidied up, since we have an opportunity to come up with a better plan before this gets merged soon? Thanks, - Chris. -- Chris Ball <cjb@xxxxxxxxxx> <http://printf.net/> One Laptop Per Child -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
