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:31:28 -0500 [thread overview]
Message-ID: <20080210093128.GA11350@infradead.org> (raw)
In-Reply-To: <20080210091757.GA17341@elte.hu>
> +#ifdef UART_CAP_UUE
> + if (up->capabilities & UART_CAP_UUE)
> +#else
> + if (up->port.type == PORT_XSCALE)
> +#endif
This looks very odd. Can anyone explain what's going on here?
Especially as UART_CAP_UUE is defined in drivers/serial/8250.h
unconditionally.
> diff --git a/drivers/serial/kgdboc.c b/drivers/serial/kgdboc.c
> new file mode 100644
> index 0000000..5079d32
> --- /dev/null
> +++ b/drivers/serial/kgdboc.c
> @@ -0,0 +1,164 @@
> +/*
> + * drivers/serial/kgdboc.c
Didn't you say there was no file left with these?
> diff --git a/include/asm-generic/kgdb.h b/include/asm-generic/kgdb.h
> new file mode 100644
> index 0000000..115972e
> --- /dev/null
> +++ b/include/asm-generic/kgdb.h
Didn't you agree to kill this file in one of the last mails?
> +#ifndef __ASSEMBLY__
> +static inline void arch_kgdb_breakpoint(void)
> +{
> + asm(" int $3");
> +}
> +# define BREAK_INSTR_SIZE 1
> +# define CACHE_FLUSH_IS_SAFE 1
> +#endif
this ifdef should go away.
> +#endif /* _ASM_KGDB_H_ */
> +#endif /* __KERNEL__ */
and the __KERNEL__ aswell as these files are in no way exported
to userspace.
> +/*
> + * kgdb_get_shadow_thread - Get the shadowed &task_struct of @threadid.
> + * @regs: The &struct pt_regs of the current thread.
> + * @threadid: The thread id of the shadowed process to get information on.
> + *
> + * RETURN:
> + * This returns a pointer to the &struct task_struct of the shadowed
> + * thread, @threadid.
> + */
> +extern struct task_struct *kgdb_get_shadow_thread(struct pt_regs *regs,
> + int threadid);
So we have kerneldoc comments in both places now? Didn't you say
you converted these to something else?
> +++ b/kernel/kgdb.c
> @@ -0,0 +1,2019 @@
> +/*
> + * kernel/kgdb.c
Another one.
next prev parent reply other threads:[~2008-02-10 9:31 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 [this message]
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
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=20080210093128.GA11350@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
all inboxes | Powered by JetHome®