From: krishna <krishna.c@globaledgesoft.com>
To: jonathan@jonmasters.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: How to understand flow of kernel code
Date: Mon, 06 Dec 2004 19:52:16 +0530 [thread overview]
Message-ID: <41B46B18.5030707@globaledgesoft.com> (raw)
Hi jon,
Thank you. I am able to use UML.
Regards,
Krishna Chaitanya
next reply other threads:[~2004-12-06 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 14:22 krishna [this message]
2004-12-06 18:49 ` How to understand flow of kernel code Jon Masters
-- strict thread matches above, loose matches on Subject: below --
2004-12-03 15:09 krishna
2004-12-03 15:27 ` Josh Boyer
2004-12-02 18:28 Nick Warne
2004-12-02 19:13 ` Randy.Dunlap
2004-12-02 19:48 ` Cal Peake
2004-12-02 4:46 krishna
2004-12-02 6:21 ` Bernd Eckenfels
2004-12-02 16:11 ` Jeff V. Merkey
2004-12-04 16:39 ` Manu Abraham
2004-12-04 14:51 ` Jon Masters
2004-12-27 20:22 ` David Eger
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=41B46B18.5030707@globaledgesoft.com \
--to=krishna.c@globaledgesoft.com \
--cc=jonathan@jonmasters.org \
--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 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.