public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joshua Hoblitt <josh@hoblitt.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org,
	j_kernel@hoblitt.com
Subject: Re: [Bug 11388] New: 2.6.27-rc3 warns about MTRR range; only 3 of 16gb of memory is usable
Date: Thu, 21 Aug 2008 14:29:52 -1000	[thread overview]
Message-ID: <20080822002952.GG23377@hoblitt.com> (raw)
In-Reply-To: <86802c440808211728r4b5a7a37w929c2dd68616361d@mail.gmail.com>

Lol.  No - I thought you implied it was in the tip tree.  Sigh.  I'll
try again.

-J

--
On Thu, Aug 21, 2008 at 05:28:51PM -0700, Yinghai Lu wrote:
> On Thu, Aug 21, 2008 at 5:10 PM, Joshua Hoblitt <josh@hoblitt.com> wrote:
> > The dmesg from the tip kernel is attached and it's at least larger than
> > the last builds dmesg.
> 
> did you apply my debug patch?
> you should get msr print out...
> 
> YH

  reply	other threads:[~2008-08-22  0:30 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11388-27@http.bugzilla.kernel.org/>
2008-08-21  1:04 ` [Bug 11388] New: 2.6.27-rc3 warns about MTRR range; only 3 of 16gb of memory is usable Andrew Morton
2008-08-21  1:20   ` Yinghai Lu
2008-08-21  1:49     ` Yinghai Lu
2008-08-21 11:44       ` Ingo Molnar
2008-08-21 11:56         ` Ingo Molnar
2008-08-21 15:39           ` Yinghai Lu
2008-08-22  3:51             ` Ingo Molnar
2008-08-22  4:45               ` Yinghai Lu
2008-08-21 20:55       ` Joshua Hoblitt
2008-08-21 21:51         ` Yinghai Lu
2008-08-21 23:33           ` Joshua Hoblitt
2008-08-22  0:10             ` Joshua Hoblitt
2008-08-22  0:28               ` Yinghai Lu
2008-08-22  0:29                 ` Joshua Hoblitt [this message]
2008-08-22  1:00                   ` Joshua Hoblitt
2008-08-22  1:10                     ` Joshua Hoblitt
2008-08-22  1:55                       ` Yinghai Lu
2008-08-22  2:15                         ` Joshua Hoblitt
2008-08-22  2:26                           ` Yinghai Lu
2008-08-22  3:24                             ` Yinghai Lu
2008-08-22  3:50                               ` Ingo Molnar
2008-08-22  3:56                                 ` Ingo Molnar
2008-08-22  4:48                                   ` Yinghai Lu
2008-08-23  0:22                                     ` Joshua Hoblitt
2008-08-23  5:52                                       ` Yinghai Lu
2008-08-23 10:43                                         ` Ingo Molnar
2008-08-26  8:35                                           ` Joshua Hoblitt
2008-08-26  8:42                                             ` Ingo Molnar
2008-08-25 21:43                                   ` Joshua Hoblitt
2008-08-22  6:16                                 ` Yinghai Lu
2008-08-22  6:24                                   ` Ingo Molnar
2008-08-23 23:53                                     ` Arjan van de Ven
2008-08-25  9:17                                       ` Ingo Molnar
2008-08-22  3:26                             ` Joshua Hoblitt

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=20080822002952.GG23377@hoblitt.com \
    --to=josh@hoblitt.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=j_kernel@hoblitt.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yhlu.kernel@gmail.com \
    /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