From: sylvanino b <sylvanino@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: how to make a contribution
Date: Sat, 12 Feb 2005 22:49:15 +0100 [thread overview]
Message-ID: <d14685de0502121349c2d5521@mail.gmail.com> (raw)
Hi,
I am writing to get some advice and general information.
I wrote a kernel tool for my personnal usage which goal is to keep a
record of recent task preemptions and interruptions that appears under
linux. Although the record is short (a few minutes only), It can help
to analyse scheduling algorithm efficiency and also driver timing
issues. The user can access data from user-space, through proc
filesystem and analyze it with a graphics tool. Then, since it's alsa
availlable within KDB, it can give clues and help for debugging.
So far, the tool is not a big deal, but not trivial either. When It is
running, the tool doesn't overload the system. And when it is not
running, it's just transparent.
I would like to share this tool if somebody is interested, but I dont
know how to proceed, I mean how to make a contribution an efficient
way. Any help/idea/information is welcome.
Thanks,
Sylvanino
next reply other threads:[~2005-02-12 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 21:49 sylvanino b [this message]
2005-02-13 2:36 ` how to make a contribution Lee Revell
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=d14685de0502121349c2d5521@mail.gmail.com \
--to=sylvanino@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox