From: "H. Peter Anvin" <hpa@zytor.com>
To: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
Cc: "'Greg KH'" <greg@kroah.com>,
"'karim@opersys.com'" <karim@opersys.com>,
"'Martin Hicks'" <mort@wildopensource.com>,
"'Daniel Stekloff'" <dsteklof@us.ibm.com>,
"'Patrick Mochel'" <mochel@osdl.org>,
"'Randy.Dunlap'" <rddunlap@osdl.org>,
"'pavel@ucw.cz'" <pavel@ucw.cz>,
"'jes@wildopensource.com'" <jes@wildopensource.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'wildos@sgi.com'" <wildos@sgi.com>,
"'Tom Zanussi'" <zanussi@us.ibm.com>
Subject: Re: [patch] printk subsystems
Date: Mon, 21 Apr 2003 11:30:11 -0700 [thread overview]
Message-ID: <3EA438B3.1010602@zytor.com> (raw)
In-Reply-To: <A46BBDB345A7D5118EC90002A5072C780C263699@orsmsx116.jf.intel.com>
Perez-Gonzalez, Inaky wrote:
>
> Hey! Come on! You don't think I am that lame, do you? Man what
> a fame I do have!
>
> Before the device vaporizes, it recalls the message, so there is
> no message to read - the same way you take away the sysfs data from
> the sysfs tree ...
>
If you think that will happen with printk(), then, quite frankly, you're
seriously deluded.
-hpa
next prev parent reply other threads:[~2003-04-21 18:18 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 18:23 [patch] printk subsystems Perez-Gonzalez, Inaky
2003-04-21 18:30 ` H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-24 18:56 Manfred Spraul
2003-04-24 19:10 ` bob
2003-04-23 0:28 Perez-Gonzalez, Inaky
2003-04-22 22:53 Perez-Gonzalez, Inaky
2003-04-23 3:58 ` Tom Zanussi
2003-04-22 19:02 Perez-Gonzalez, Inaky
2003-04-22 19:03 ` H. Peter Anvin
2003-04-22 21:52 ` Tom Zanussi
2003-04-22 18:46 Perez-Gonzalez, Inaky
2003-04-22 23:28 ` Karim Yaghmour
2003-04-22 5:09 Perez-Gonzalez, Inaky
2003-04-24 18:22 ` bob
2003-04-22 4:02 Perez-Gonzalez, Inaky
2003-04-22 5:52 ` Karim Yaghmour
2003-04-22 6:04 ` Tom Zanussi
2003-04-22 3:04 Perez-Gonzalez, Inaky
2003-04-22 6:00 ` Tom Zanussi
2003-04-22 2:49 Perez-Gonzalez, Inaky
2003-04-22 4:34 ` Karim Yaghmour
2003-04-21 18:42 Perez-Gonzalez, Inaky
2003-04-17 19:58 Perez-Gonzalez, Inaky
2003-04-17 20:34 ` Karim Yaghmour
2003-04-17 21:03 ` Perez-Gonzalez, Inaky
2003-04-17 21:37 ` Tom Zanussi
2003-04-18 7:21 ` Tom Zanussi
2003-04-18 7:42 ` Greg KH
2003-04-21 15:56 ` Karim Yaghmour
2003-04-08 23:15 Chuck Ebbert
2003-04-07 20:13 Martin Hicks
2003-04-08 18:41 ` Pavel Machek
2003-04-08 20:02 ` Jes Sorensen
2003-04-08 21:02 ` Pavel Machek
2003-04-08 21:10 ` H. Peter Anvin
2003-04-08 21:57 ` Pavel Machek
2003-04-08 22:02 ` Jes Sorensen
2003-04-08 22:05 ` H. Peter Anvin
2003-04-08 22:55 ` Martin Hicks
2003-04-08 23:10 ` Randy.Dunlap
2003-04-14 18:33 ` Patrick Mochel
2003-04-14 22:33 ` Daniel Stekloff
2003-04-16 18:42 ` Patrick Mochel
2003-04-16 12:35 ` Daniel Stekloff
2003-04-16 19:16 ` Martin Hicks
2003-04-16 12:43 ` Daniel Stekloff
2003-04-17 15:56 ` Martin Hicks
2003-04-17 13:58 ` Karim Yaghmour
2003-04-15 13:27 ` Martin Hicks
2003-04-15 14:40 ` Karim Yaghmour
2003-04-08 22:00 ` Jes Sorensen
2003-04-11 19:21 ` Martin Hicks
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=3EA438B3.1010602@zytor.com \
--to=hpa@zytor.com \
--cc=dsteklof@us.ibm.com \
--cc=greg@kroah.com \
--cc=inaky.perez-gonzalez@intel.com \
--cc=jes@wildopensource.com \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=mort@wildopensource.com \
--cc=pavel@ucw.cz \
--cc=rddunlap@osdl.org \
--cc=wildos@sgi.com \
--cc=zanussi@us.ibm.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 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.