From: Jani Nikula <jani.nikula@linux.intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>
Cc: intel-gfx@lists.freedesktop.org,
dri-devel <dri-devel@lists.freedesktop.org>,
David Airlie <airlied@redhat.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>
Subject: Re: [Intel-gfx] i915 gvt broke drm-tip; Fix ASAP
Date: Mon, 24 May 2021 12:58:16 +0300 [thread overview]
Message-ID: <87k0nocv2f.fsf@intel.com> (raw)
In-Reply-To: <20210524030901.GC27293@zhen-hp.sh.intel.com>
On Mon, 24 May 2021, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> On 2021.05.22 21:19:38 +0200, Thomas Zimmermann wrote:
>> Hi,
>>
>> after creating drm-tip today as part of [1], building drm-tip is now broken
>> with the error message shown below.
>>
>> Some register constants appear to be missing from the GVT code. Please fix
>> ASAP.
>>
>
> Thanks, Thomas. Looks DMC rename missed gvt part. We need to ask CI to have
> at least build test with gvt.
Indeed. This is fixed now with 273895109a04 ("drm/i915/gvt: Add missing
macro name changes").
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>
Cc: intel-gfx@lists.freedesktop.org,
dri-devel <dri-devel@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@redhat.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
zhi.a.wang@intel.com
Subject: Re: i915 gvt broke drm-tip; Fix ASAP
Date: Mon, 24 May 2021 12:58:16 +0300 [thread overview]
Message-ID: <87k0nocv2f.fsf@intel.com> (raw)
In-Reply-To: <20210524030901.GC27293@zhen-hp.sh.intel.com>
On Mon, 24 May 2021, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> On 2021.05.22 21:19:38 +0200, Thomas Zimmermann wrote:
>> Hi,
>>
>> after creating drm-tip today as part of [1], building drm-tip is now broken
>> with the error message shown below.
>>
>> Some register constants appear to be missing from the GVT code. Please fix
>> ASAP.
>>
>
> Thanks, Thomas. Looks DMC rename missed gvt part. We need to ask CI to have
> at least build test with gvt.
Indeed. This is fixed now with 273895109a04 ("drm/i915/gvt: Add missing
macro name changes").
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2021-05-24 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 19:19 [Intel-gfx] i915 gvt broke drm-tip; Fix ASAP Thomas Zimmermann
2021-05-22 19:19 ` Thomas Zimmermann
2021-05-24 3:09 ` [Intel-gfx] " Zhenyu Wang
2021-05-24 3:09 ` Zhenyu Wang
2021-05-24 9:58 ` Jani Nikula [this message]
2021-05-24 9:58 ` Jani Nikula
2021-05-25 11:53 ` [Intel-gfx] " Thomas Zimmermann
2021-05-25 11:53 ` Thomas Zimmermann
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=87k0nocv2f.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
--cc=zhenyuw@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.