From: Arjan van de Ven <arjan@linux.intel.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch 2.6.16-rc6-mm2] x86: add NUMA to oops messages
Date: Sun, 18 Jun 2006 14:48:27 +0200 [thread overview]
Message-ID: <44954B9B.6070209@linux.intel.com> (raw)
In-Reply-To: <200606180815_MC3-1-C2CC-41A5@compuserve.com>
Chuck Ebbert wrote:
>> and putting half of .config into the oops doesn't seem
>> like a good long term strategy.
>
> It's just this one thing; I can't think of anything else to add...
>
if it's compact I'd actually put the entire vermagic line there...
it'll show compiler, preempt and a whole lot of other "distinctive" features
next prev parent reply other threads:[~2006-06-18 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 12:13 [patch 2.6.16-rc6-mm2] x86: add NUMA to oops messages Chuck Ebbert
2006-06-18 12:48 ` Arjan van de Ven [this message]
2006-06-18 17:25 ` Randy.Dunlap
2006-06-18 16:16 ` Andreas Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-06-18 8:13 Chuck Ebbert
2006-06-18 8:59 ` Andi Kleen
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=44954B9B.6070209@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=76306.1226@compuserve.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--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