From: Jani Nikula <jani.nikula@intel.com>
To: "Xu, Colin" <colin.xu@intel.com>"Xu, Colin" <colin.xu@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/i915: Update virtual PCH in single function
Date: Thu, 31 May 2018 08:59:15 +0300 [thread overview]
Message-ID: <87fu2874cs.fsf@intel.com> (raw)
In-Reply-To: <42F16D4EF370BA4795A0C5C21AFE25199317D2@SHSMSX101.ccr.corp.intel.com>
On Thu, 31 May 2018, "Xu, Colin" <colin.xu@intel.com> wrote:
> Hi Jani, any comments? Without correct PCH type, BXT in virtualization
> will fail to boot due to display initialization fail. If any more
> input required, please kindly let me know.
See [1] and please provide your Tested-by and/or Reviewed-by on the
relevant patches.
Thanks,
Jani.
[1] https://patchwork.freedesktop.org/series/43986/
--
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-05-31 5:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 4:46 [PATCH 0/2] drm/i915: Fix incorrect virtual PCH_NONE/PCH_NOP assignment colin.xu
2018-05-28 4:46 ` [PATCH 2/2] drm/i915: Assign PCH_NONE for BXT in virtualization colin.xu
2018-05-28 4:46 ` [PATCH 1/2] drm/i915: Update virtual PCH in single function colin.xu
2018-05-28 9:37 ` Jani Nikula
2018-05-28 9:48 ` Jani Nikula
2018-05-28 13:42 ` Jani Nikula
2018-05-29 0:31 ` Colin Xu
2018-05-29 5:45 ` Jani Nikula
2018-05-29 6:20 ` Colin Xu
2018-05-31 3:10 ` Xu, Colin
2018-05-31 5:59 ` Jani Nikula [this message]
2018-05-28 5:12 ` ✓ Fi.CI.BAT: success for drm/i915: Fix incorrect virtual PCH_NONE/PCH_NOP assignment Patchwork
2018-05-28 6:02 ` ✓ Fi.CI.IGT: " Patchwork
2018-05-28 13:40 ` ✗ Fi.CI.BAT: failure for drm/i915: Fix incorrect virtual PCH_NONE/PCH_NOP assignment (rev2) 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=87fu2874cs.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=colin.xu@intel.com \
--cc=intel-gfx@lists.freedesktop.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