From: Pavel Machek <pavel@ucw.cz>
To: "Brown, Len" <len.brown@intel.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] acpi: remove function tracing macros
Date: Thu, 19 Jan 2006 14:36:55 +0100 [thread overview]
Message-ID: <20060119133655.GA1558@elf.ucw.cz> (raw)
In-Reply-To: <F7DC2337C7631D4386A2DF6E8FB22B3005B835E4@hdsmsx401.amr.corp.intel.com>
Hi!
> I'm sorry, I can't apply this source clean-up patch.
>
> We need tracing to debug interpreter failures on hardware
> in the field.
Well, it seems very few people actually need that. Perhaps those
people could use separate version of instrumented interpretter?
On Linux, same can probably be done by linker magic etc. Is there
anyone needing instrumentation on *BSD?
Pavel
--
Thanks, Sharp!
next prev parent reply other threads:[~2006-01-19 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 18:14 [PATCH] acpi: remove function tracing macros Brown, Len
[not found] ` <F7DC2337C7631D4386A2DF6E8FB22B3005B835E4-N2PTB0HCzHKkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2006-01-16 18:45 ` Pekka Enberg
2006-01-19 13:36 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-16 20:01 Brown, Len
2006-01-19 13:38 ` Pavel Machek
2006-01-11 16:01 Pekka Enberg
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=20060119133655.GA1558@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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