From: Karim Yaghmour <karim@opersys.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Roman Zippel <zippel@linux-m68k.org>
Subject: [UPDATE] LTT patch for 2.5.15
Date: Fri, 10 May 2002 17:10:53 -0400 [thread overview]
Message-ID: <3CDC375D.6382AEC9@opersys.com> (raw)
Following Roman's recommendations, I've updated the LTT patch
with the following changes:
- Modified code format to match Linux coding style
- Removed overweight comments
- Changed trace macros to static inlines
- Converted uint8_t, uint32_t and uint64_t to u8, u32 and u64
- Added <asm/trace.h> for architecture-dependent definitions
I've divided the patch in 4 parts:
1- Core tracing functionality
2- Trace driver
3- Architecture-dependent trace statements (i386, ppc, mips, s/390, sh)
4- Architecture-independent trace statements
Part X is available from:
ftp://ftp.opersys.com/pub/LTT/ExtraPatches/patch-ltt-linux-2.5.15-vanilla-020510-1.14-part-X.gz
The patch is also available in one piece:
ftp://ftp.opersys.com/pub/LTT/ExtraPatches/patch-ltt-linux-2.5.15-vanilla-020510-1.14.gz
Cheers,
Karim
===================================================
Karim Yaghmour
karim@opersys.com
Embedded and Real-Time Linux Expert
===================================================
reply other threads:[~2002-05-10 21:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3CDC375D.6382AEC9@opersys.com \
--to=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@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 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.