mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: jason.wessel@windriver.com, linux-kernel@vger.kernel.org
Subject: Re: kgdb: core
Date: Mon, 21 Apr 2008 21:46:36 -0700	[thread overview]
Message-ID: <20080421214636.617970c6.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080421141252.GR9554@elte.hu>

> On Mon, 21 Apr 2008 16:12:52 +0200 Ingo Molnar <mingo@elte.hu> wrote:
> > So please
> > 
> > a) make this a kerneldoc comment and
> > 
> > b) remove the kerneldoc at the definition site(s).
> > 
> > (alternative: teach the kerneldoc system to go fishing in the various 
> > arch directories to find the appropriate documentation, but I don't 
> > know enough about kerneldoc to be able say anything about that).
> 
> well there's lkml feedback ping-pong effect here. It was pointed out in 
> earlier kgdb review that it's an "error" to put kerneldoc into header 
> files.

It is, normally.  Nobody thought about this case.

> I pointed out that it makes no sense to do otherwise but removed 
> the kerneldoc annotation to resolve the "objection".

Duplicating the same stuff in multiple places is the larger sin.  It sounds
like the best compromise would be to kernel-doc the interface in the .h
file and remove the duplicated comments from .c.

Or perhaps we kernel-doc the interface in the x86 .c files and leave it at
that - people should go there to find the docs.  Problem is, this will
presumably generate bad results if one builds the formal kerneldoc output
for a different architecture.  The kerneldoc system could of course fix
this somehow, but I don't know what shape it would take nor how much work
it would be.

  reply	other threads:[~2008-04-22  4:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200804181741.m3IHfTeC012089@hera.kernel.org>
2008-04-18 22:09 ` Andrew Morton
2008-04-21 14:12   ` Ingo Molnar
2008-04-22  4:46     ` Andrew Morton [this message]
2008-04-22  8:30       ` Ingo Molnar
2008-04-22 15:25       ` Randy Dunlap
2008-04-22 20:57         ` Andrew Morton
2008-04-22 21:02           ` Randy Dunlap
2008-04-22 21:19             ` Jason Wessel
2008-04-23  1:19               ` 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=20080421214636.617970c6.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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