From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] Fix early access to per-cpu variables
Date: Fri, 08 Aug 2008 02:39:01 +0000 [thread overview]
Message-ID: <20080808023901.GE26567@sgi.com> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA3083844C8@orsmsx505.amr.corp.intel.com>
On Thu, Aug 07, 2008 at 02:41:11PM -0700, Luck, Tony wrote:
> If that machine covers most of the bases ... then it should be
I have since booted it on all but two of our configs (those machines
were busy and already booked). They are not significantly different
from the others.
> good enough. Did you set CONFIG_PRINTK_TIME=y? I belatedly
Yes.
Thanks,
Robin
prev parent reply other threads:[~2008-08-08 2:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 21:04 [RFC] Fix early access to per-cpu variables Luck, Tony
2008-08-07 21:30 ` Robin Holt
2008-08-07 21:41 ` Luck, Tony
2008-08-08 2:39 ` Robin Holt [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=20080808023901.GE26567@sgi.com \
--to=holt@sgi.com \
--cc=linux-ia64@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