Hi, On Wed, Aug 29 2012, IAN CHEN wrote: > For several MoviNAND, there are some known issue with secure option. > For these specific MoviNAND device, we skip secure option. > > You could refer this discussion in XDA developers. > http://forum.xda-developers.com/showthread.php?t=1644364 > https://plus.google.com/111398485184813224730/posts/21pTYfTsCkB#111398485184813224730/posts/21pTYfTsCkB > > Signed-off-by: Ian Chen <[email protected]> > Reviewed-by: Namjae Jeon <[email protected]> > Acked-by: Jaehoon Chung <[email protected]> > Reviewed-by: Linus Walleij <[email protected]>
Thanks. We should explain the nature of the bug in the commit message, so that users and the stable@ maintainers know how bad the problem is by reading the patch. (This should go to stable@, right? Do you know which kernel versions are affected?) I'll add something like this, unless you have a better proposal: == For several MoviNAND, there are some known issues with secure option. For these specific MoviNAND device, we skip secure option. Specifically, there is a bug in the eMMC firmware that causes unrecoverable corruption when the MMC is erased with MMC_CAP_ERASE enabled. You could refer this discussion in XDA developers. http://forum.xda-developers.com/showthread.php?t=1644364 https://plus.google.com/111398485184813224730/posts/21pTYfTsCkB#111398485184813224730/posts/21pTYfTsCkB == - Chris. -- Chris Ball <[email protected]> <http://printf.net/> One Laptop Per Child -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

