From: Christoph Hellwig <hch@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@zip.com.au>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Wessel <jason.wessel@windriver.com>
Subject: Re: [3/6] kgdb: core
Date: Sun, 10 Feb 2008 04:11:23 -0500 [thread overview]
Message-ID: <20080210091123.GA19912@infradead.org> (raw)
In-Reply-To: <20080210085735.GA13466@elte.hu>
On Sun, Feb 10, 2008 at 09:57:35AM +0100, Ingo Molnar wrote:
> > It would be nice if you could move the kerneldoc comments to the
> > proper place at least. [...]
>
> i'd agree in general but this is really a special case, please look at
> the context. This would duplicate all the kerneldoc headers for all
> architectures. We'd have to move the same kerneldoc header to all
> architecture arch/*/kernel/kgdb.c files. It's much nicer in
> asm-generic/kgdb.h.
Well, the point of kerneldoc comments is that they're reasily
extractable. If you want to document the arch interface a pure
text document in Documentation/ might be a better choice.
> > Also it seems at least some of Jan's patches are missing aswell.
>
> i dont think so. Which ones do you mean? I just reviewed them and they
> are either already done, or moot (for kgdb complications that i objected
> to and removed from this kgdb-x86 tree).
The one I noticed quickly is the __ASSEMBLY__ removal from
asm-x86/kgdb.h. I haven't looked at the serial bits because I don't
think I'm qualified to comment on those, but I'm also not seeing any
replies to any of his patches. Especially the comments on the arch
interface seem like something that should be acted upon to me.
next prev parent reply other threads:[~2008-02-10 9:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 7:13 Ingo Molnar
2008-02-10 7:31 ` Sam Ravnborg
2008-02-10 7:59 ` Ingo Molnar
2008-02-10 7:35 ` Christoph Hellwig
2008-02-10 7:43 ` Ingo Molnar
2008-02-10 7:57 ` Christoph Hellwig
2008-02-10 8:02 ` Ingo Molnar
2008-02-10 8:21 ` Ingo Molnar
2008-02-10 8:26 ` Christoph Hellwig
2008-02-10 9:08 ` Ingo Molnar
2008-02-10 9:17 ` Ingo Molnar
2008-02-10 9:20 ` Ingo Molnar
2008-02-10 9:34 ` Ingo Molnar
2008-02-10 9:31 ` Christoph Hellwig
2008-02-10 17:17 ` [patch] kgdb light, v6 Ingo Molnar
2008-02-10 19:43 ` Bartlomiej Zolnierkiewicz
2008-02-10 21:31 ` Ingo Molnar
2008-02-10 20:55 ` Bartlomiej Zolnierkiewicz
2008-02-10 21:09 ` Ingo Molnar
2008-02-10 21:45 ` Jan Kiszka
2008-02-10 22:14 ` Bartlomiej Zolnierkiewicz
2008-02-10 22:32 ` Jan Kiszka
2008-02-10 22:40 ` Ingo Molnar
2008-02-11 2:35 ` Yinghai Lu
2008-02-10 22:31 ` Ingo Molnar
2008-02-10 22:24 ` Bartlomiej Zolnierkiewicz
2008-02-10 8:24 ` [3/6] kgdb: core Christoph Hellwig
2008-02-10 8:57 ` Ingo Molnar
2008-02-10 9:11 ` Christoph Hellwig [this message]
2008-02-10 9:27 ` Ingo Molnar
2008-02-10 9:34 ` Christoph Hellwig
2008-02-10 17:02 ` Ingo Molnar
2008-02-10 12:46 ` Marcin Slusarz
2008-02-10 13:19 ` Jesper Juhl
2008-02-10 14:00 ` Marcin Slusarz
2008-02-10 13:36 ` Jan Kiszka
2008-02-10 16:43 ` Ingo Molnar
2008-02-10 19:20 ` Bartlomiej Zolnierkiewicz
2008-02-10 16:46 ` Ingo Molnar
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=20080210091123.GA19912@infradead.org \
--to=hch@infradead.org \
--cc=akpm@zip.com.au \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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