Hi! > I've had this for a while, and converting to a GIT repository is > incentive enough to send it out. Mostly it just makes existing > diagnostics be more useful, but it also adds some error checking > for cases that can happen on non-trivial systems ... or when > userspace actions through /sys/.../power/state files break some > system integrity rules. > > If nobody objects, I'll probably ask to merge this at some point. Patch is good, but merging it is going to be slightly tricky because I'll need to touch the same area just after 2.6.12... (pm_message_t-becomes-struct will conflict in trivial way). I could create pm_message_t-becomes-struct patch early, and put it into good-git repository so that you could put your patch on the top of that. Would that work for you? [Another alternative is make this go in *real fast* so that it gets in before 2.6.12 and I can place my patch on the top of that.] Pavel -- Boycott Kodak -- for their patent abuse against Java.
