From: Jason Wessel <jason.wessel@windriver.com>
To: Randy Dunlap <RANDY.DUNLAP@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: kgdb: core
Date: Tue, 22 Apr 2008 16:19:55 -0500 [thread overview]
Message-ID: <480E567B.6060708@windriver.com> (raw)
In-Reply-To: <5739699.1208898133855.JavaMail.oracle@acsmt302.oracle.com>
Randy Dunlap wrote:
> --- Original Message --- (akpm wrote:)
>>> On Tue, 22 Apr 2008 08:25:19 -0700 Randy Dunlap
<randy.dunlap@oracle.com> wrote:
>>>
>>> kernel-doc output doesn't depend on build $ARCH.
>> Ah, interesting. I made an ass of u and me.
>>
>> In that case documentng them in x86 .c and leaving all other definitions
>> and declarations uncommented sounds the way to go?
>
> Yes, that would be fine and traditional (historical).
>
> ~Randy
>
So is the summary here that we cannot just document the actual
interface API in the incude/linux/kgdb.h?
The problem I had here was pretty simple in that not all of the
functions in the API are used by all the archs. It seemed pretty
reasonable at the time to just document everything in the .h file
because it was more for the folks who wanted to add kgdb support to an
arch and of little to no use to end users of kgdb.
The mainline only has a small chunk of the docs right now because not
all of kgdb is merged. I was just hoping it was real easy to generate
some reasonable looking docs. The docs for all the kgdb code that
exists (in mainline and not in mainline) can be viewed here as an
example.
http://kernel.org/pub/linux/kernel/people/jwessel/kgdb/
Jason.
next prev parent reply other threads:[~2008-04-22 21:21 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 ` kgdb: core Andrew Morton
2008-04-21 14:12 ` Ingo Molnar
2008-04-22 4:46 ` Andrew Morton
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 [this message]
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=480E567B.6060708@windriver.com \
--to=jason.wessel@windriver.com \
--cc=RANDY.DUNLAP@oracle.com \
--cc=akpm@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).