From: "Joshua Hudson" <joshudson@gmail.com>
To: "Chuck Ebbert" <76306.1226@compuserve.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] i386: print stack size in oops messages
Date: Mon, 5 Jun 2006 14:26:44 -0700 [thread overview]
Message-ID: <bda6d13a0606051426u43e5a744x99c500df93cc9267@mail.gmail.com> (raw)
In-Reply-To: <200606042309_MC3-1-C19F-CFFE@compuserve.com>
On 6/4/06, Chuck Ebbert <76306.1226@compuserve.com> wrote:
> Always print stack size in oops messages. By having this line
> in every message, ugly newline logic can be removed as well.
>
> Signed-off-by: Chuck Ebbert <76306.1226@compuserve.com>
Thank you. Since I always use preempt (it saved me from more than
one hard crash when kernel debugging), this is useful too me.
prev parent reply other threads:[~2006-06-05 21:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 3:07 Chuck Ebbert
2006-06-05 21:26 ` Joshua Hudson [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=bda6d13a0606051426u43e5a744x99c500df93cc9267@mail.gmail.com \
--to=joshudson@gmail.com \
--cc=76306.1226@compuserve.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
all inboxes | Powered by JetHome®