On Wed, Nov 6, 2013 at 10:42 AM, Fabio Estevam <festevam@xxxxxxxxx> wrote: > On Wed, Nov 6, 2013 at 4:08 PM, Brian Norris > <computersforpeace@xxxxxxxxx> wrote: >> I seriously doubt that a total revert is the correct answer to this >> problem. Can you pick up the discussion with Huang on the mailing > > Agree that it would be better to come up with a better localized fix > rather than the complete revert, but I currently don't have the time > to spend on debugging this issue. OK. And if Huang doesn't have the time to clean up his mess, then we will have to revert things. > On the other hand, I would not like to see mx23 broken in 3.12 because > of this. It can't even reach the prompt. 3.12 is already out the door, so we now have some time to get a proper fix into -stable. >> list, or at least explain what the actual root cause is? Have you been >> going through some private communication on this issue? A proper >> bugfix with an identified issue is preferable to a blind revert. > > No private communication. I reported this issue in the mailing list: > http://lists.infradead.org/pipermail/linux-mtd/2013-November/049641.html Right. But this ended with you pointing Huang to the right U-boot setup, then everything went silent. And today, I get a blunt revert request from you as well as an independent DMA fix from Huang. Since you guys are both from Freescale, I wasn't sure if there was any coordination/correlation, or if this is really as uncoordinated as it looks. Brian -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html