linux-kernel - [PATCH 0/5] Clean up patches

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20081002150529.087488257@goodmis.org>
Date:	Thu, 02 Oct 2008 11:05:29 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Andrew Morton <akpm@...ux-foundation.org>
Subject: [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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/