From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Wed, 5 Jul 2017 14:32:40 +0200
Subject: Kernel header inclusion practice
In-Reply-To: <34715BDE-086F-4ADA-BAF8-FB0435781519@introo.me>
References: <CAJQX3DxAap_pUXXA3DNEnqQp2JGWzbsXw=zaXyKLim0NUFV6nQ@mail.gmail.com>
	<20170705120742.GB9714@kroah.com>
	<34715BDE-086F-4ADA-BAF8-FB0435781519@introo.me>
Message-ID: <20170705123240.GA26951@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

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 :)