From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Zwane Mwaikambo <zwane@linux.realnet.co.sz>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
Kernel Janitors <kernel-janitor-discuss@lists.sourceforge.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] printk prefix cleanups.
Date: Tue, 12 Feb 2002 02:37:31 -0500 [thread overview]
Message-ID: <3C68C63B.8A785890@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0202120923350.30276-100000@netfinity.realnet.co.sz>
Zwane Mwaikambo wrote:
>
> On Tue, 12 Feb 2002, Pete Zaitcev wrote:
>
> > > Here is a simple patch which reduces resultant binary size by 1.2k for
> > > this particular module (opl3sa2). [...]
> >
> > > #define OPL3SA2_MODULE_NAME "opl3sa2"
> > > +#define OPL3SA2_PFX OPL3SA2_MODULE_NAME ": "
> >
> > > - printk(KERN_ERR "opl3sa2: MSS mixer not installed?\n");
> > > + printk(KERN_ERR OPL3SA2_PFX "MSS mixer not installed?\n");
> >
> > I do not believe that it shortens binaries. Care to quote
> > size(1) output and /proc/modules with and without the patch?
>
> It does _not_ reduce the memory footprint, that i knew before doing the
> patch, the only thing it does do is reduce the resultant binary's
> filesize. Surely thats worth it just for the space saving? size(1) reports
> the same sizes for both patched and unpatched.
If size(1) reports the same size, then no.
But I would still support a patch that added just 'PFX' to the driver...
Jeff
--
Jeff Garzik | "I went through my candy like hot oatmeal
Building 1024 | through an internally-buttered weasel."
MandrakeSoft | - goats.com
next prev parent reply other threads:[~2002-02-12 7:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1013495822.30629.linux-kernel2news@redhat.com>
2002-02-12 7:18 ` [PATCH] printk prefix cleanups Pete Zaitcev
2002-02-12 7:26 ` Zwane Mwaikambo
2002-02-12 7:37 ` Jeff Garzik [this message]
2002-02-12 7:46 ` Zwane Mwaikambo
2002-02-12 6:26 Zwane Mwaikambo
2002-02-12 6:46 ` Jeff Garzik
2002-02-12 9:50 ` Horst von Brand
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=3C68C63B.8A785890@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=kernel-janitor-discuss@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
--cc=zwane@linux.realnet.co.sz \
/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