From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Jeremy Fitzhardinge <jeremy@xensource.com>,
Chris Wright <chrisw@sous-sol.org>,
Steven Rostedt <srostedt@redhat.com>
Subject: Re: [PATCH 5/5] xen: nuke the ballon files
Date: Thu, 02 Oct 2008 08:34:52 -0700 [thread overview]
Message-ID: <48E4EA1C.2090808@goop.org> (raw)
In-Reply-To: <20081002151105.025170721@goodmis.org>
Steven Rostedt wrote:
> Investigating the unused static files in the balloon code, I discovered
> that the balloon code is not used at all.
>
> The header file is one big #if 0 and all the functions in the C file
> is static. There is no caller like init_module to hook to any of
> these functions. Basically, this code is one big patch of dead code
> wasting space on my hard drive.
>
> This patch removes the balloon code altogether since there are no
> users.
>
Er, I think you should back away from that crack pipe.
> -subsys_initcall(balloon_init);
J
next prev parent reply other threads:[~2008-10-02 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 15:05 [PATCH 0/5] Clean up patches Steven Rostedt
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 [this message]
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=48E4EA1C.2090808@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=srostedt@redhat.com \
/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