From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: lucas.demarchi@intel.com
Subject: Re: drm/i915: virtual PCH and PCH_NOP fixes
Date: Mon, 11 Jun 2018 15:09:36 +0300 [thread overview]
Message-ID: <87bmch4j9b.fsf@intel.com> (raw)
In-Reply-To: <20180608123330.31003-1-jani.nikula@intel.com>
On Fri, 08 Jun 2018, Jani Nikula <jani.nikula@intel.com> wrote:
> Just a resend of [1] with Lucas' patch added.
And pushed, thanks for the review and testing.
BR,
Jani.
>
> BR,
> Jani.
>
> [1] http://mid.mail-archive.com/20180531115624.30269-1-jani.nikula@intel.com
>
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-06-11 12:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 12:33 drm/i915: virtual PCH and PCH_NOP fixes Jani Nikula
2018-06-08 12:33 ` [PATCH 1/5] drm/i915: fix guest virtual PCH detection on non-PCH systems Jani Nikula
2018-06-08 12:33 ` [PATCH 2/5] drm/i915: document PCH_NOP Jani Nikula
2018-06-08 12:33 ` [PATCH 3/5] drm/i915: clean up virtual PCH special case handling Jani Nikula
2018-06-08 12:33 ` [PATCH 4/5] drm/i915: be more strict about HAS_PCH_NOP() usage Jani Nikula
2018-06-08 12:33 ` [PATCH 5/5] drm/i915: fix PCH_NOP setting for non-PCH platforms Jani Nikula
2018-06-08 13:02 ` ✓ Fi.CI.BAT: success for series starting with [1/5] drm/i915: fix guest virtual PCH detection on non-PCH systems Patchwork
2018-06-08 15:38 ` ✓ Fi.CI.IGT: " Patchwork
2018-06-11 12:09 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-31 11:56 drm/i915: virtual PCH and PCH_NOP fixes Jani Nikula
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=87bmch4j9b.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@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;
as well as URLs for NNTP newsgroup(s).