[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170103092317.slzmtrdzzrjzbypw@zhen-hp.sh.intel.com>
Date: Tue, 3 Jan 2017 17:23:17 +0800
From: Zhenyu Wang <zhenyuw@...ux.intel.com>
To: Alex Williamson <alex.williamson@...hat.com>,
Jani Nikula <jani.nikula@...el.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Intel Graphics <intel-gfx@...ts.freedesktop.org>,
DRI <dri-devel@...ts.freedesktop.org>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Jike Song <jike.song@...el.com>
Subject: Re: linux-next: build failure after merge of the drm-intel-fixes tree
On 2017.01.02 21:48:57 -0700, Alex Williamson wrote:
> > Alex, I liked to have kvmgt related mdev interface change be merged through
> > vfio tree, but wasn't awared one of Jike's fix had conflict. Could you apply
> > below fix in your tree? I think in general for possible interface change in
> > future we still need a pull request for i915 to resolve dependence earlier.
>
> Hi Zhenyu,
>
> Hopefully this abstraction will help to isolate vendor drivers from
> mdev API changes in the future. I can certainly roll this patch into
> the original to maintain bisectability. I want to get these changes in
> for rc3, will a pull request for the i915 changes be sent this week?
Send to Jani who is managing i915 fixes pull.
--
Open Source Technology Center, Intel ltd.
$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
Download attachment "signature.asc" of type "application/pgp-signature" (164 bytes)
Powered by blists - more mailing lists