From: Pavel Machek <pavel@suse.cz>
To: Don Zickus <dzickus@redhat.com>
Cc: linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: [PATCH] x86 clean up nmi panic messages
Date: Sat, 27 May 2006 16:33:28 +0000 [thread overview]
Message-ID: <20060527163328.GD4242@ucw.cz> (raw)
In-Reply-To: <20060526175902.GB2839@redhat.com>
Hi!
> Clean up some of the output messages on the nmi error paths to make more
> sense when they are displayed. This is mainly a cosmetic fix and
> shouldn't impact any normal code path.
>
> Signed-off-by: Don Zickus <dzickus@redhat.com>
ACK.
> Pavel,
>
> I hope this patch addresses your concerns. This will apply on top of my
> other patch.
Yes, thanks.
--
Thanks for all the (sleeping) penguins.
prev parent reply other threads:[~2006-05-27 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 21:49 [PATCH] Allow users to force a panic on NMI Don Zickus
2006-05-18 19:17 ` Pavel Machek
2006-05-25 17:39 ` Paul Jackson
2006-05-25 21:45 ` Pavel Machek
2006-05-26 17:59 ` [PATCH] x86 clean up nmi panic messages Don Zickus
2006-05-27 16:33 ` Pavel Machek [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=20060527163328.GD4242@ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=dzickus@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.