mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Randy Dunlap <rdunlap@xenotime.net>
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:55:02 +0100	[thread overview]
Message-ID: <1327308902.2442.256.camel@twins> (raw)
In-Reply-To: <4F1B0BFC.2010105@xenotime.net>

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?

Also, what the difference between Ekernel and Ikernel?

>  !Iinclude/linux/completion.h
>  !Ekernel/timer.c
>       </sect1>




  reply	other threads:[~2012-01-23  8:55 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 [this message]
2012-01-23 17:17   ` Randy Dunlap

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=1327308902.2442.256.camel@twins \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdunlap@xenotime.net \
    --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