[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1255681467.32489.360.camel@localhost>
Date: Fri, 16 Oct 2009 11:24:27 +0300
From: Artem Bityutskiy <dedekind1@...il.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Simon Kagstrom <simon.kagstrom@...insight.net>,
linux-mtd <linux-mtd@...ts.infradead.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
David Woodhouse <dwmw2@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
"Koskinen Aaro (Nokia-D/Helsinki)" <aaro.koskinen@...ia.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH v9 4/5] core: Add kernel message dumper to call on
oopses and panics
On Fri, 2009-10-16 at 10:09 +0200, Ingo Molnar wrote:
> * Simon Kagstrom <simon.kagstrom@...insight.net> wrote:
>
> /**
> * kmsg_dump_register - register a kernel log dumper.
> * @dump: pointer to the kmsg_dumper structure
> *
> * Adds a kernel log dumper to the system. The dump callback in the
> * structure will be called when the kernel oopses or panics and must be
> * set. Returns zero on success and -EINVAL or -EBUSY otherwise.
> */
>
> Small detail - please use the KernelDoc style used in existing printk.c
> facilities, i.e. use a single space instead of a tab:
>
> /**
> * kmsg_dump_register - register a kernel log dumper.
> * @dump: pointer to the kmsg_dumper structure
> *
> * Adds a kernel log dumper to the system. The dump callback in the
> * structure will be called when the kernel oopses or panics and must be
> * set. Returns zero on success and -EINVAL or -EBUSY otherwise.
> */
And then %-EINVAL and %-EBUSY.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists