From: Abramo Bagnara <abramo@alsa-project.org>
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com, alan@lxorguk.ukuu.org.uk
Subject: Re: patch for 2.4.0 disable printk and panic messages, third try
Date: Sun, 28 Jan 2001 16:14:46 +0100 [thread overview]
Message-ID: <3A743766.98DACE29@alsa-project.org> (raw)
In-Reply-To: <01012815533500.01191@deepthought.seibold.net>
Stefani Seibold wrote:
>
> Hi guys,
>
> this is now the third try to release my patch for disabling all kernel
> messages. It is usefull on deep embedded systems with no human interactions
> and for rescue discs where the diskspace is always to less.
>
> This patch has now the following features:
>
> The macro printk throws away all parameters and calls now a funciton "inline
> int printk_inline(void)" which always return 0 integer. So it should be now
> compatibel to the original printk funciton.
>
Then I suppose that you've checked that never in kernel printk arguments
have side effects, don't you ;-)
printk("%d", p());
printk("%d", a++);
etc.
You're changing semantics of a well known function and also if you don't
broke anything now, what grants this for the future?
You need also a big warning in printk documentation: "Note that
arguments may to be not evaluated" and hope everybody note it.
I'd prefer to rely on modern compiler smartness.
--
Abramo Bagnara mailto:abramo@alsa-project.org
Opera Unica Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy
ALSA project is http://www.alsa-project.org
sponsored by SuSE Linux http://www.suse.com
It sounds good!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-28 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 14:53 patch for 2.4.0 disable printk and panic messages, third try Stefani Seibold
2001-01-28 15:10 ` Dmitry A. Fedorov
2001-01-28 15:14 ` Abramo Bagnara [this message]
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=3A743766.98DACE29@alsa-project.org \
--to=abramo@alsa-project.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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