From: "Elliott, Robert (Persistent Memory)" <elliott@hpe.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>,
"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
"bp@alien8.de" <bp@alien8.de>,
"mingo@kernel.org" <mingo@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"hpa@zytor.com" <hpa@zytor.com>,
"toshi.kani@hp.com" <toshi.kani@hp.com>
Cc: "airlied@redhat.com" <airlied@redhat.com>,
"benh@kernel.crashing.org" <benh@kernel.crashing.org>,
"mst@redhat.com" <mst@redhat.com>,
"vinod.koul@intel.com" <vinod.koul@intel.com>,
"jgross@suse.com" <jgross@suse.com>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"luto@amacapital.net" <luto@amacapital.net>,
"davem@davemloft.net" <davem@davemloft.net>,
"ben@decadent.org.uk" <ben@decadent.org.uk>,
"benjamin.poirier@gmail.com" <benjamin.poirier@gmail.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"corbet@lwn.net" <corbet@lwn.net>
Subject: RE: [PATCH v2] x86: PAT: Documentation: rewrite "MTRR effects on PAT / non-PAT systems"
Date: Sat, 5 Mar 2016 04:39:58 +0000 [thread overview]
Message-ID: <94D0CD8314A33A4D9D801C0FE68B40295C350C7C@G9W0745.americas.hpqcorp.net> (raw)
In-Reply-To: <1457131501-14855-1-git-send-email-mcgrof@kernel.org>
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> owner@vger.kernel.org] On Behalf Of Luis R. Rodriguez
> Sent: Friday, March 04, 2016 4:45 PM
> Subject: [PATCH v2] x86: PAT: Documentation: rewrite "MTRR effects on
> PAT / non-PAT systems"
...
> +MMIO and another PCI BAR for write-combing, if needed.
typo: combining
next prev parent reply other threads:[~2016-03-05 4:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 21:21 [PATCH] x86: PAT: Documentation: update overlapping ioremap hack recommendation Luis R. Rodriguez
2016-03-03 21:21 ` Luis R. Rodriguez
2016-03-03 21:42 ` Paul E. McKenney
2016-03-03 21:42 ` Paul E. McKenney
2016-03-04 19:23 ` Luis R. Rodriguez
2016-03-04 19:23 ` Luis R. Rodriguez
2016-03-04 21:09 ` Paul E. McKenney
2016-03-04 22:45 ` [PATCH v2] x86: PAT: Documentation: rewrite "MTRR effects on PAT / non-PAT systems" Luis R. Rodriguez
2016-03-04 22:45 ` Luis R. Rodriguez
2016-03-05 0:03 ` Paul E. McKenney
2016-03-05 0:03 ` Paul E. McKenney
2016-03-05 1:03 ` Luis R. Rodriguez
2016-03-05 1:03 ` Luis R. Rodriguez
2016-03-05 4:39 ` Elliott, Robert (Persistent Memory) [this message]
2016-03-15 22:21 ` Luis R. Rodriguez
2016-03-15 22:21 ` Luis R. Rodriguez
2016-03-05 11:52 ` Ingo Molnar
2016-03-05 11:52 ` Ingo Molnar
2016-03-15 22:24 ` Luis R. Rodriguez
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=94D0CD8314A33A4D9D801C0FE68B40295C350C7C@G9W0745.americas.hpqcorp.net \
--to=elliott@hpe.com \
--cc=airlied@redhat.com \
--cc=ben@decadent.org.uk \
--cc=benh@kernel.crashing.org \
--cc=benjamin.poirier@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@kernel.org \
--cc=mingo@kernel.org \
--cc=mst@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hp.com \
--cc=vinod.koul@intel.com \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).