public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Stefani Seibold <stefani@seibold.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: patch for 2.4.0 disable printk
Date: Sun, 28 Jan 2001 11:44:38 +1100	[thread overview]
Message-ID: <3A736B76.214D4193@uow.edu.au> (raw)
In-Reply-To: <01012723313500.01190@deepthought.seibold.net>

Stefani Seibold wrote:
> 
> Second, i had change the macro so it calls now a inline funciton
> printk_inline which always return 0. So it should be now compatibel to the
> standard printk funciton.

A #define is better.

You see, even if printk is a null inline function,

	printk("foo");

will still cause "foo" to appear in your output. Apparently
very recent versions of gcc have fixed this.

BTW: Graham Stoney prepared a similar patch for 2.2 last year.
You may be able to borrow some ideas from that work, and the
followup discussion.

http://www.uwsg.iu.edu/hypermail/linux/kernel/0004.2/0709.html

-
-
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/

  reply	other threads:[~2001-01-28  0:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-27 22:31 patch for 2.4.0 disable printk Stefani Seibold
2001-01-28  0:44 ` Andrew Morton [this message]
2001-01-28  9:27   ` Stefani Seibold
2001-01-28 17:32     ` Jamie Lokier
2001-01-29  2:48   ` Paul Gortmaker
  -- strict thread matches above, loose matches on Subject: below --
2001-01-26 20:46 Stefani Seibold
2001-01-26 21:13 ` David Weinehall
2001-01-26 11:05 Stefani Seibold
2001-01-27  0:09 ` Thunder from the hill
2001-01-27 10:57   ` Stefani Seibold
2001-01-29 17:40     ` James Simmons
2001-01-29 20:17       ` Stefani Seibold

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=3A736B76.214D4193@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefani@seibold.net \
    /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