Andy Green wrote: > ~ - We didn't bang on the new suspend / resume enough.
By the way, we have a buglet in S3C MCI resume: it tries to re-register while the MMC core is still asleep, which yields a friendly "mmc mmc0:0001: parent mmc0 should not be sleeping" from device_pm_add. Not sure if we actually care - it doesn't seem to cause any real trouble. > ~ - we have not banged on Balaji's changed driver code enough. It's a > very big change. Ah yes, that one's major. How do we go about this ? My lab is currently about 2/3 busy, so if necessary, I could add another machine for some light automated testing. > ~ - I dunno that we banged on the new WLAN stack stuff enough either I gave it quite a solid beating not too long ago, but it can't hurt to kick it a few more times. My focus is on communication with/through the module, since we're unlikely to have picked up any new gremlins in the higher layers. > ~ - sysfs changes need handling (lack of them also impact Balaji changes > testing I think) Let's hope the distribution makers hear the call to arms :-) > That's all the known issues in mind, situation is now pretty decent. Sounds pretty good, yes. - Werner
