From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Denys Vlasenko <vda.linux@googlemail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
R.E.Wolff@BitWizard.nl
Subject: Re: [PATCH] drivers/char/specialix.c: stop inlining largish static functions
Date: Wed, 9 Apr 2008 00:15:17 +0200 [thread overview]
Message-ID: <20080408221517.GB24755@bitwizard.nl> (raw)
In-Reply-To: <47FBE5C3.1040105@gmail.com>
On Tue, Apr 08, 2008 at 11:38:11PM +0200, Jiri Slaby wrote:
>
> - static const char *badmagic =
> + static const char badmagic[] =
> KERN_ERR "sx: Warning: bad specialix port magic number for
> device %s in %s\n";
[...]
> if (port->magic != SPECIALIX_MAGIC) {
> printk(badmagic, name, routine);
> return 1;
> }
In a galaxy, far, far away, someone thought that this would save
memory. Especially if you print a message multiple times, the compiler
usually doesn't merge the string constants of two copies of:
printk (KERN_ERR "Bad magic number...");
Maybe it does now. (I don't think I came up with this. I probably
copied it over from somewhere....)
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
next prev parent reply other threads:[~2008-04-08 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 10:44 Denys Vlasenko
2008-04-08 11:43 ` Rogier Wolff
2008-04-08 12:10 ` Alan Cox
2008-04-08 21:38 ` Jiri Slaby
2008-04-08 22:15 ` Rogier Wolff [this message]
2008-04-08 22:18 ` Denys Vlasenko
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=20080408221517.GB24755@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=vda.linux@googlemail.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
Powered by JetHome