public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH 0/8] replacing/fixing printk with pr_debug/pr_info in arch/i386 - intro
Date: Sun, 17 Oct 2004 11:23:42 -0700	[thread overview]
Message-ID: <1098037422.20419.21.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.GSO.4.61.0410172006060.27743@waterleaf.sonytel.be>

On Sun, 2004-10-17 at 20:10 +0200, Geert Uytterhoeven wrote:
> Iff you ever want to replace the above, make sure to do it like this:
>     printk_info("Start... ");
>     ...
>     printkc_info("Ok!\n");
> 
> (with `printkc_info()' being a continuation of `printk_info()'. And do the same
> for all other KERN_* variations. This would add real value, since the next step
> is to make the printk{,c}_*() definitions conditionally empty for embedded
> systems and/or systems with few memory.
> 
> Gr{oetje,eeting}s,

I suggest this is the incorrect usage.
Start then Continue then End.
I suppose one could use Continue/End with an implied start
or simply End (ie:  printk)

cheers,  joe

  reply	other threads:[~2004-10-17 18:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-17 17:10 [PATCH 0/8] replacing/fixing printk with pr_debug/pr_info in arch/i386 - intro Daniele Pizzoni
2004-10-17 16:19 ` Ingo Molnar
2004-10-17 18:10   ` Geert Uytterhoeven
2004-10-17 18:23     ` Joe Perches [this message]
2004-10-17 18:34       ` Geert Uytterhoeven
2004-10-18  2:41   ` Daniele Pizzoni
2004-10-18 10:36     ` Ingo Molnar
2004-10-18 12:59       ` Daniele Pizzoni
     [not found] <2QlVm-7u4-13@gated-at.bofh.it>
     [not found] ` <2Qmok-7KK-1@gated-at.bofh.it>
2004-10-17 20:26   ` Andi Kleen

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=1098037422.20419.21.camel@localhost.localdomain \
    --to=joe@perches.com \
    --cc=geert@linux-m68k.org \
    /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