From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to understand flow of kernel code
Date: Thu, 02 Dec 2004 11:13:50 -0800 [thread overview]
Message-ID: <41AF696E.7060703@osdl.org> (raw)
In-Reply-To: <200412021828.07990.nick@linicks.net>
Nick Warne wrote:
>>Interesting trivia. Krishna in hindi means "all attractive". The Greeks
>>took the word and
>>over time it was corrupted into the word "Christ" which was later used
>>for Jesus of Nazereth.
>>I lot of people probably don't know his last name actually came from the
>>Vedic culture.
>
>
> So I presume the 'Hare' bit came from that famous race with the tortoise...
>
> JK'ing aside, good tips - I am trying to learn also to enable me to debug oops
> I get here and report properly back to the devs.
Besides reading the code, Denis Vlasenko
<vda@port.imtp.ilyichevsk.odessa.ua> has written & posted:
Subject: [RFC] HOWTO find oops location, v2
on 2004.Aug.15. Find it in an lkml email archive.
--
~Randy
next prev parent reply other threads:[~2004-12-02 19:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 18:28 How to understand flow of kernel code Nick Warne
2004-12-02 19:13 ` Randy.Dunlap [this message]
2004-12-02 19:48 ` Cal Peake
-- strict thread matches above, loose matches on Subject: below --
2004-12-06 14:22 krishna
2004-12-06 18:49 ` Jon Masters
2004-12-03 15:09 krishna
2004-12-03 15:27 ` Josh Boyer
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=41AF696E.7060703@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
/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