: Clean up boot time console messages
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest10 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/10 | : Quiet HVSI boot outputdrivers/ | +1 | 0 replies | |
| 2/10 | : Quiet time init outputarch/ | +2 | 0 replies | |
| 3/10 | : Quiet page order outputarch/ | +1 | 0 replies | |
| 4/10 | : Quiet VETH version printkdrivers/ | +1 | 0 replies | |
| 5/10 | : Don't print chosen idle loop at every bootarch/ arch/ arch/ +1 more | +7 | 0 replies | |
| 6/10 | : Less verbose mem configuration outputarch/ arch/ | +7 | 0 replies | |
| 7/10 | : Lack of ISA interrupts on XICS isn't dangerousarch/ | +1 | 0 replies | |
| 8/10 | : Quiet PCI init printoutsarch/ | +5 | 0 replies | |
| 9/10 | : Quiet rtasd output at bootarch/ | +3 | 0 replies | |
| 10/10 | : Quiet oprofile output at bootarch/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [0/10]: Clean up boot time console messages
Here's a series of patches that removes a bunch of console messages during PPC boot. They are moved to KERN_DEBUG instead, which means that:
1. They will still be in dmesg.
2. If needed for debugging, they can be enabled by adding "loglevel=8" to the boot command line.
But for most uses, I don't see how these messages really add value to the user. The information is normally available at other places, and mostly needed when trying to figure out why something doesn't work right.
Since these are all janitorial, I'd appreciate them being queued for 2.6.18.
-Olof