From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Ben Widawsky <benjamin.widawsky@intel.com>,
Imre Deak <imre.deak@intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/cnl: Avoid ioremap_wc on Cannonlake as well.
Date: Mon, 14 Aug 2017 15:13:21 +0300 [thread overview]
Message-ID: <1502712801.10154.6.camel@linux.intel.com> (raw)
In-Reply-To: <CABVU7+uUYkSq-qzFjOPizYRzXaYrbY+jQk+Fi7nGT1w9gY4WCw@mail.gmail.com>
On Fri, 2017-08-11 at 17:36 -0700, Rodrigo Vivi wrote:
> On Fri, Aug 11, 2017 at 4:39 PM, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> > WC is apparently not an option for CNL+ on GTT here.
> > Trying to use it we get hard hangs.
> >
> > Credits-to: Ben Widawsky <benjamin.widawsky@intel.com>
I guess "Suggested-by:"/"Reported-by:" would be the standard one :)
Do update the comment above the code, too.
Do we have a "Bspec:" one? Would make it easier to review.
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-08-14 12:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 23:39 [PATCH] drm/i915/cnl: Avoid ioremap_wc on Cannonlake as well Rodrigo Vivi
2017-08-12 0:11 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-08-12 0:36 ` [PATCH] " Rodrigo Vivi
2017-08-14 12:13 ` Joonas Lahtinen [this message]
2017-08-14 17:24 ` Vivi, Rodrigo
2017-08-29 23:09 ` Rodrigo Vivi
2017-08-30 11:13 ` Joonas Lahtinen
2017-08-30 11:26 ` Chris Wilson
2017-08-30 11:38 ` Joonas Lahtinen
2017-08-30 17:58 ` Vivi, Rodrigo
2017-08-31 8:27 ` Joonas Lahtinen
2017-08-31 16:45 ` Vivi, Rodrigo
2017-08-30 0:16 ` ✓ Fi.CI.BAT: success for drm/i915/cnl: Avoid ioremap_wc on Cannonlake as well. (rev2) Patchwork
2017-08-30 4:33 ` ✗ Fi.CI.IGT: warning " Patchwork
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=1502712801.10154.6.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=benjamin.widawsky@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@gmail.com \
--cc=rodrigo.vivi@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