Clean up patches
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | xen: clean up labelarch/ | +2 | 0 replies | |
| 2/5 | xen: remove unused function warningsarch/ | +4 | 0 replies | |
| 3/5 | xen: nuke dead code in enlighten.carch/ | +0 | 0 replies | |
| 4/5 | sound: update snd_assert macroinclude/ | +7 | 2 replies | |
| 5/5 | xen: nuke the ballon filesdrivers/ drivers/ include/ | +0 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] Clean up patches
Like other kernel developers, I compile kernels several times a day with various configs. Some are for testing, others are given to me by others to debug some code.
I like to look at any warnings that gcc gives me, and lately I've been irritated by the same warnings appearing in the same places that has nothing to do with my code.
The biggest offender is the Xen code. I figured that I'll take a look at what these warnings are and if they are trivial, I'll fix them.
The thing that got me when looking into this, is most of the warnings in Xen come from dead code! Code that is not called by anyone, or has references by #if 0 code.
There was one patch from the sound code that only needed a more robust macro when the debugging was not configured.
The rest of the patches get rid of most of my warnings. There are a few left where gcc complains about discarding qualifier types but those are not as trivial to fix, so I'll leave them to those maintainers.
-- Steve