Prev: [PATCH 3/6] tracing, vmscan: Add trace event when a page is written
Next: [PROPOSAL - FIRST POST] NMI & register clash handling infrastructure
From: Rafael J. Wysocki on 8 Jun 2010 05:10
Hi,

I decided to split this big patch into a series of smaller ones addressing one
issue each. I think all of the issues addressed by [2-5/5] may be regarded as
regressions from 2.6.33, because that kernel didn't have these problems.

[1/5] - Not really a fix, but [2/5] depends on it and I don't see a reason to
duplicate that thing even more.
[2/5] - Low-level GPE manipulation fix
[3/5] - Fix possible issue with re-enabling a GPE after event handling
[4/5] - Fix the initialization of GPEs
[5/5] - Fix GPE sysfs interface

Please review, possibly apply.

Thanks,
Rafael

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: [PATCH 3/6] tracing, vmscan: Add trace event when a page is written
Next: [PROPOSAL - FIRST POST] NMI & register clash handling infrastructure