From: Tim Bird <tim.bird@am.sony.com>
To: karim@opersys.com
Cc: Roger Luethi <rl@hellgate.ch>,
Robert Wisniewski <bob@watson.ibm.com>,
zanussi@us.ibm.com, linux-kernel@vger.kernel.org,
richardj_moore@uk.ibm.com, michel.dagenais@polymtl.ca
Subject: Re: LTT user input
Date: Tue, 27 Jul 2004 16:51:36 -0700 [thread overview]
Message-ID: <4106EA88.10707@am.sony.com> (raw)
In-Reply-To: <410410F9.5030403@opersys.com>
Karim Yaghmour wrote:
> Plus, I've run into a ton of people who have told me that this type of
> tool is essential for their day-to-day work. I will stop short of
> covering actual names, but you should hear about such things in the near
> future.
Sony has used LTT in the past, and we plan to use it for a few more
development projects underway currently. It would be nice if we
didn't have to wait for all the pieces to fall together for each
new kernel release (arch support, trace point patches, desired
sub-system stability). Having seen LTT used for a number of years,
I'd have to agree with Karim's assessment that it would probably
be "neater" today if so much time hadn't been spent over the
years wrangling it into the kernel.
=============================
Tim Bird
Architecture Group Co-Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
E-mail: tim.bird@am.sony.com
=============================
next prev parent reply other threads:[~2004-07-27 23:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 20:47 LTT user input zanussi
2004-07-23 10:01 ` Roger Luethi
2004-07-23 17:34 ` zanussi
2004-07-23 19:19 ` Roger Luethi
2004-07-23 20:44 ` zanussi
2004-07-23 22:06 ` Roger Luethi
2004-09-01 16:36 ` zanussi
2004-07-23 22:40 ` Robert Wisniewski
2004-07-23 23:45 ` Roger Luethi
2004-07-25 19:58 ` Karim Yaghmour
2004-07-25 21:10 ` Roger Luethi
2004-07-27 23:51 ` Tim Bird [this message]
2004-07-28 2:48 ` Todd Poynor
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=4106EA88.10707@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=bob@watson.ibm.com \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michel.dagenais@polymtl.ca \
--cc=richardj_moore@uk.ibm.com \
--cc=rl@hellgate.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox