linux-kernel - Re: linux-next: build failure after merge of the drm-intel-fixes tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170103150709.543d4f75@canb.auug.org.au>
Date:   Tue, 3 Jan 2017 15:07:18 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Zhenyu Wang <zhenyuw@...ux.intel.com>
Cc:     Daniel Vetter <daniel.vetter@...ll.ch>,
        Intel Graphics <intel-gfx@...ts.freedesktop.org>,
        DRI <dri-devel@...ts.freedesktop.org>,
        Alex Williamson <alex.williamson@...hat.com>,
        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

Hi Zhenyu,

On Tue, 3 Jan 2017 10:59:29 +0800 Zhenyu Wang <zhenyuw@...ux.intel.com> 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.

This only happens because I merge both trees (I think) ...

-- 
Cheers,
Stephen Rothwell