From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel header inclusion practice
Date: Wed, 5 Jul 2017 14:32:40 +0200 [thread overview]
Message-ID: <20170705123240.GA26951@kroah.com> (raw)
In-Reply-To: <34715BDE-086F-4ADA-BAF8-FB0435781519@introo.me>
On Wed, Jul 05, 2017 at 08:13:08PM +0800, Shiyao Ma wrote:
> Thanks!
>
> > On 5 Jul 2017, at 20:07, Greg KH <greg@kroah.com> wrote:
> >
> >>
> >> If there is any documentation about the API of the headers (e.g., what
> >> they include), that will be great.
> >
> > What exactly do you mean by this?
>
>
> I mean if any kernel documentation specifies what the headers provide,
> IOW, what they include, and what functions/variables they declare.
>
> So I guess probably not, the source code of kernel headers are their
> own documentation/specification.
Yes, the source itself is always the best documentation, it's always
kept up to date :)
prev parent reply other threads:[~2017-07-05 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 6:50 Kernel header inclusion practice Shiyao MA
2017-07-05 12:07 ` Greg KH
2017-07-05 12:13 ` Shiyao Ma
2017-07-05 12:32 ` Greg KH [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=20170705123240.GA26951@kroah.com \
--to=greg@kroah.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).