public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Ross <chris@tebibyte.org>
To: Jim Nelson <james4765@verizon.net>
Cc: Graeme T Ford <gtford@gmail.com>,
	linux lover <linux.lover2004@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Understanding how kernel functions works and adding new one
Date: Sun, 26 Dec 2004 11:00:42 +0100	[thread overview]
Message-ID: <41CE8BCA.5090503@tebibyte.org> (raw)
In-Reply-To: <41CD67D8.6080001@verizon.net>



Jim Nelson escreveu:
> I'll second that.  Google is probably the closest thing to Microsoft's 
> Knowlege Base that Linux has for quick questions ;) .

Especially if you use Google's Linux specific section 
http://www.google.com/linux

Regards,
Chris R.

      parent reply	other threads:[~2004-12-26 10:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-25  4:20 Understanding how kernel functions works and adding new one linux lover
2004-12-25  9:09 ` Graeme T Ford
2004-12-25 13:15   ` Jim Nelson
2004-12-25 20:04     ` Pedro Venda
2004-12-28 20:38       ` Lee Revell
2004-12-26  4:16     ` sean
2004-12-26 10:00     ` Chris Ross [this message]

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=41CE8BCA.5090503@tebibyte.org \
    --to=chris@tebibyte.org \
    --cc=gtford@gmail.com \
    --cc=james4765@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.lover2004@gmail.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