From: Yinghai Lu <yinghai@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Arjan van de Ven <arjan@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: make mtrr code could use debugpat
Date: Fri, 03 Apr 2009 17:49:40 -0700 [thread overview]
Message-ID: <49D6AEA4.3080907@kernel.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0904031737030.3915@localhost.localdomain>
Linus Torvalds wrote:
>
> On Fri, 3 Apr 2009, Yinghai Lu wrote:
>> only print out get_mtrr when debugpat
>
> Is that get_mtrr message really so interesting that it needs to be printed
> out at all? Even with debugpat?
or you pick the one in tip/master that remove those line.
YH
next prev parent reply other threads:[~2009-04-04 0:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090329205805.GA24693@elte.hu>
[not found] ` <20090329210103.GA24901@elte.hu>
[not found] ` <49CFF517.30001@kernel.org>
[not found] ` <alpine.LFD.2.00.0903291553210.3948@localhost.localdomain>
[not found] ` <1238434120.4529.783.camel@localhost.localdomain>
[not found] ` <20090403175555.GH6295@elte.hu>
[not found] ` <alpine.LFD.2.00.0904031203400.4015@localhost.localdomain>
[not found] ` <20090403212152.GA3493@linux-os.sc.intel.com>
[not found] ` <alpine.LFD.2.00.0904031443340.7007@localhost.localdomain>
[not found] ` <alpine.LFD.2.00.0904031521460.3915@localhost.localdomain>
[not found] ` <20090403222928.GA6446@elte.hu>
2009-04-03 22:35 ` [PATCH] x86: make mtrr code could use debugpat Yinghai Lu
2009-04-04 0:37 ` Linus Torvalds
2009-04-04 0:48 ` Yinghai Lu
2009-04-04 0:49 ` Yinghai Lu [this message]
2009-04-04 0:50 ` Yinghai Lu
2009-04-04 1:18 ` Ingo Molnar
2009-04-04 6:39 ` Jaswinder Singh Rajput
2009-04-04 6:52 ` Jaswinder Singh Rajput
2009-04-04 7:09 ` Jaswinder Singh Rajput
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=49D6AEA4.3080907@kernel.org \
--to=yinghai@kernel.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=venkatesh.pallipadi@intel.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