From: WANG Cong <xiyou.wangcong@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] move x86 specific oops=panic to generic code
Date: Fri, 28 Jan 2011 07:31:06 +0000 (UTC) [thread overview]
Message-ID: <ihtrbq$921$1@dough.gmane.org> (raw)
In-Reply-To: 20110127221511.GA32313@aepfle.de
On Thu, 27 Jan 2011 23:15:11 +0100, Olaf Hering wrote:
> The oops=panic cmdline option is not x86 specific, move it to generic
> code. Update documentation.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
>
Reviewed-by: WANG Cong <xiyou.wangcong@gmail.com>
prev parent reply other threads:[~2011-01-28 7:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 22:15 [PATCH] move x86 specific oops=panic to generic code Olaf Hering
2011-01-28 7:31 ` WANG Cong [this message]
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='ihtrbq$921$1@dough.gmane.org' \
--to=xiyou.wangcong@gmail.com \
--cc=linux-kernel@vger.kernel.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