Re: [Intel-gfx] linux-next: build failure after merge of the drm-intel-fixes tree

From	Alex Williamson <alex.williamson@redhat.com>
Newsgroups	linux.kernel
Subject	Re: [Intel-gfx] linux-next: build failure after merge of the drm-intel-fixes tree
Date	2017-01-03 21:40 +0100
Message-ID	<sVE2e-37A-3@gated-at.bofh.it> (permalink)
References	<sVkwx-5RO-1@gated-at.bofh.it> <sVnE5-8fN-15@gated-at.bofh.it> <sVpcR-Jg-1@gated-at.bofh.it> <sVtzQ-4gf-11@gated-at.bofh.it> <sVxk6-6WU-25@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Tue, 03 Jan 2017 15:25:24 +0200
Jani Nikula <jani.nikula@intel.com> wrote:

> On Tue, 03 Jan 2017, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> > 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.  
> 
> Send what to me? I've pushed fixes to drm-intel-fixes today for testing,
> and expect to send a pull request to Dave early Thursday. If there's a
> conflict, it can usually be solved while merging, like Stephen has done.

Unless there's some preference otherwise, I was only asking if the i915
changes were queued for rc3 such that I could trail behind them and
fixup the mdev API change without relying on it getting caught in the
merge.  If we're happy to do it at merge time, I won't worry about it.
Thanks,

Alex

Thread

linux-next: build failure after merge of the drm-intel-fixes tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-01-03 00:50 +0100
  Re: linux-next: build failure after merge of the drm-intel-fixes tree Zhenyu Wang <zhenyuw@linux.intel.com> - 2017-01-03 04:10 +0100
    Re: linux-next: build failure after merge of the drm-intel-fixes  tree Stephen Rothwell <sfr@canb.auug.org.au> - 2017-01-03 05:10 +0100
    Re: linux-next: build failure after merge of the drm-intel-fixes  tree Alex Williamson <alex.williamson@redhat.com> - 2017-01-03 05:50 +0100
      Re: linux-next: build failure after merge of the drm-intel-fixes tree Zhenyu Wang <zhenyuw@linux.intel.com> - 2017-01-03 10:30 +0100
        Re: [Intel-gfx] linux-next: build failure after merge of the   drm-intel-fixes tree Jani Nikula <jani.nikula@intel.com> - 2017-01-03 14:30 +0100
          Re: [Intel-gfx] linux-next: build failure after merge of the  drm-intel-fixes tree Alex Williamson <alex.williamson@redhat.com> - 2017-01-03 21:40 +0100
            Re: [Intel-gfx] linux-next: build failure after merge of the  drm-intel-fixes tree Daniel Vetter <daniel@ffwll.ch> - 2017-01-04 10:10 +0100

csiph-web