From: Dave Airlie <airlied@redhat.com>
To: mcgrof@suse.com, torvalds@linux-foundation.org,
dan.j.williams@intel.com, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: x86 PAT memtype regression fixes (with extra cc's)
Date: Mon, 24 Oct 2016 16:31:44 +1000 [thread overview]
Message-ID: <1477290706-7696-1-git-send-email-airlied@redhat.com> (raw)
As per Ingo's request I've cc'ed a bunch more x86/PAT people.
Dave.
next reply other threads:[~2016-10-24 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 6:31 Dave Airlie [this message]
2016-10-24 6:31 ` [PATCH 1/2] x86/io: add interface to reserve io memtype for a resource range. (v1.1) Dave Airlie
2016-10-25 9:40 ` Ingo Molnar
2016-10-25 11:10 ` Thomas Gleixner
2016-10-25 17:31 ` Luis R. Rodriguez
2016-10-26 5:49 ` Daniel Vetter
2016-10-26 6:12 ` Dave Airlie
2016-10-26 7:00 ` Daniel Vetter
2016-10-26 17:48 ` [PATCH] x86/pat, mm: Make track_pfn_insert() return void Borislav Petkov
2016-10-24 6:31 ` [PATCH 2/2] drm/drivers: add support for using the arch wc mapping API Dave Airlie
2016-10-24 9:24 ` Christian König
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=1477290706-7696-1-git-send-email-airlied@redhat.com \
--to=airlied@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@suse.com \
--cc=torvalds@linux-foundation.org \
--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).