On Sun, 2 Sep 2007, Jeff Garzik wrote:I'll post the info as a reply to the first mail in this series. I have fairly recent gcc (4.1.1) and I don't see us dropping support for it in the next few years. Well, uninitialized_var() is definitely more greppable than "= 0" which code all over does all the time :-) Anyway, the point is that the warnings are bogus anyway (hence maintainers Cc:'ed so that they can confirm if I arrived at the conclusion correctly) /and/ that uninitialized_var() stands out sorely, so I don't see bugs getting "hidden" at all -- in fact I did find two bugs during this process, and fixed them accordingly. Thanks, Satyam
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Linus Torvalds | Linux 2.6.27-rc5 |
| Jared Hulbert | [PATCH 00/10] AXFS: Advanced XIP filesystem |
| Linus Torvalds | Linux 2.6.27-rc8 |
git: | |
| David Miller | [GIT]: Networking |
| Antonio Almeida | HTB accuracy for high speed |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
