From: "Christopher Friesen" <cfriesen@nortelnetworks.com>
To: davidm@hpl.hp.com
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Andrew Morton <akpm@zip.com.au>,
j-nomura@ce.jp.nec.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.16 kernel/printk.c (per processorinitializationcheck)
Date: Fri, 07 Dec 2001 17:14:11 -0500 [thread overview]
Message-ID: <3C113F33.B310CB10@nortelnetworks.com> (raw)
In-Reply-To: <3C103A1E.2524A7B7@zip.com.au> <Pine.LNX.4.21.0112071651360.22868-100000@freak.distro.conectiva> <15377.13976.342104.636304@napali.hpl.hp.com>
David Mosberger wrote:
>
> >>>>> On Fri, 7 Dec 2001 16:52:07 -0200 (BRST), Marcelo Tosatti <marcelo@conectiva.com.br> said:
>
> Marcelo> I'm really not willing to apply this kludge...
>
> Do you agree that it should always be safe to call printk() from C code?
Is it really safe to call this from interrupt handlers? I can think of cases
where the time required to print can totally mess stuff up...
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2001-12-07 22:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 5:46 [PATCH] 2.4.16 kernel/printk.c (per processor initialization check) j-nomura
2001-12-03 9:20 ` Andrew Morton
2001-12-03 10:32 ` j-nomura
2001-12-04 1:45 ` [PATCH] 2.4.16 kernel/printk.c (per processor initializationcheck) Andrew Morton
2001-12-06 5:01 ` j-nomura
2001-12-07 3:40 ` [PATCH] 2.4.16 kernel/printk.c (per processorinitializationcheck) Andrew Morton
2001-12-07 18:52 ` Marcelo Tosatti
2001-12-07 20:52 ` William Lee Irwin III
2001-12-07 21:37 ` David Mosberger
2001-12-07 20:47 ` Marcelo Tosatti
2001-12-07 22:17 ` David Mosberger
2001-12-07 21:09 ` Marcelo Tosatti
2001-12-08 1:10 ` David Mosberger
2001-12-08 11:27 ` Alan Cox
2001-12-08 16:41 ` David Mosberger
2001-12-08 20:45 ` Alan Cox
2001-12-09 0:32 ` David Mosberger
2001-12-09 0:55 ` Alan Cox
2001-12-09 0:58 ` David Mosberger
2001-12-09 1:15 ` Alan Cox
2001-12-09 1:14 ` David Mosberger
2001-12-09 1:32 ` Alan Cox
2001-12-07 22:08 ` Alan Cox
2001-12-07 22:14 ` Christopher Friesen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-08 17:36 Manfred Spraul
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=3C113F33.B310CB10@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=akpm@zip.com.au \
--cc=davidm@hpl.hp.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.