All of lore.kernel.org
 help / color / mirror / Atom feed
From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: LKM related API documentation
Date: Sun, 4 May 2014 11:07:58 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1405041106540.8186@localhost> (raw)
In-Reply-To: <CA+aCy1F5ZVTAsfJdEJ82+hJfzUC09a_iwpn6=jK9vn0tiJX4rQ@mail.gmail.com>

On Sun, 4 May 2014, Pranay Srivastava wrote:

>
>
> On Sunday, May 4, 2014, Abhijeet Kasurde <abhijeetkasurde21@gmail.com> wrote:
> > Hi All,
> >
> > Can anyone point me to any location of documentation related to Linux
> > Kernel Module APIs ?
> >
> > I am specifically looking for following APIs -
> >
> > 1. find_symbol
> > 2. request_module
> > 3. find_module etc.
> >
> hi Abhijeet,
>
> read the code. Its really simple to understand all the three above.
> I don't think any documentation on these specifically. But the usage
> is quite simple. Try to look up some modules that use them.

  you could always generate the documentation from the kerneldoc
content. i wrote a wiki page on that once, i think the page is still
accurate:

http://www.crashcourse.ca/wiki/index.php/Kerneldoc

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

  reply	other threads:[~2014-05-04 15:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-04 12:41 LKM related API documentation Abhijeet Kasurde
2014-05-04 15:00 ` Pranay Srivastava
2014-05-04 15:07   ` Robert P. J. Day [this message]
2014-05-04 17:19     ` Abhijeet Kasurde

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=alpine.LFD.2.11.1405041106540.8186@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=kernelnewbies@lists.kernelnewbies.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.