From: Randy Dunlap <rdunlap@xenotime.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 14/14] docbook: fix sched source file names in device-drivers book
Date: Mon, 23 Jan 2012 09:17:56 -0800 [thread overview]
Message-ID: <4F1D9644.7090707@xenotime.net> (raw)
In-Reply-To: <1327308902.2442.256.camel@twins>
On 01/23/2012 12:55 AM, Peter Zijlstra wrote:
> On Sat, 2012-01-21 at 11:03 -0800, Randy Dunlap wrote:
>> From: Randy Dunlap <rdunlap@xenotime.net>
>>
>> Fix warning since kernel scheduler functions and kernel-doc
>> notation were moved to other files.
>>
>> docproc: lnx-33-rc1/kernel/sched.c: No such file or directory
>>
>> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
>> Cc: Ingo Molnar <mingo@elte.hu>
>> Cc: Peter Zijlstra <peterz@infradead.org>
>> ---
>> Documentation/DocBook/device-drivers.tmpl | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> --- lnx-33-rc1.orig/Documentation/DocBook/device-drivers.tmpl
>> +++ lnx-33-rc1/Documentation/DocBook/device-drivers.tmpl
>> @@ -50,7 +50,9 @@
>>
>> <sect1><title>Delaying, scheduling, and timer routines</title>
>> !Iinclude/linux/sched.h
>> -!Ekernel/sched.c
>> +!Ekernel/sched/core.c
>> +!Ikernel/sched/cpupri.c
>> +!Ikernel/sched/fair.c
>
> There's more files in there, they might not include proper kerneldoc
> comments, but shouldn't they be included anyway?
Only the ones that have kernel-doc comments are listed here.
> Also, what the difference between Ekernel and Ikernel?
!Efilename
is for files that contain exported symbols and it only lists the exports.
!Ifilename
is for files that contain kernel-doc for internal functions.
It is OK to use both of them for one filename so that both exports and
internal functions are listed in the generated output.
>> !Iinclude/linux/completion.h
>> !Ekernel/timer.c
>> </sect1>
>
>
>
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2012-01-23 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 19:03 Randy Dunlap
2012-01-23 8:55 ` Peter Zijlstra
2012-01-23 17:17 ` Randy Dunlap [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=4F1D9644.7090707@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome