public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/5] Clean up patches
Date: Thu, 02 Oct 2008 11:05:29 -0400	[thread overview]
Message-ID: <20081002150529.087488257@goodmis.org> (raw)

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


             reply	other threads:[~2008-10-02 15:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 15:05 Steven Rostedt [this message]
2008-10-02 15:05 ` [PATCH 1/5] xen: clean up label Steven Rostedt
2008-10-02 15:05 ` [PATCH 2/5] xen: remove unused function warnings Steven Rostedt
2008-10-02 15:05 ` [PATCH 3/5] xen: nuke dead code in enlighten.c Steven Rostedt
2008-10-02 15:05 ` [PATCH 4/5] sound: update snd_assert macro Steven Rostedt
2008-10-03  9:10   ` Takashi Iwai
2008-10-03 14:24     ` Steven Rostedt
2008-10-02 15:05 ` [PATCH 5/5] xen: nuke the ballon files Steven Rostedt
2008-10-02 15:34   ` Jeremy Fitzhardinge
2008-10-02 17:59     ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081002150529.087488257@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox