From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753970AbdGUTCE (ORCPT ); Fri, 21 Jul 2017 15:02:04 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47594 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751504AbdGUTCC (ORCPT ); Fri, 21 Jul 2017 15:02:02 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 32B9A1E2E8 Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=hdegoede@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 32B9A1E2E8 Subject: Re: linux-next: build failure after merge of the drm-misc tree To: Daniel Vetter , Stephen Rothwell Cc: Dave Airlie , Intel Graphics , DRI , Greg KH , Linux-Next Mailing List , Linux Kernel Mailing List References: <20170719114657.245537cd@canb.auug.org.au> <20170721100833.48c8fa9d@canb.auug.org.au> From: Hans de Goede Message-ID: <0e9187d2-7c7c-d531-0df6-839be9410eb9@redhat.com> Date: Fri, 21 Jul 2017 21:01:59 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.30]); Fri, 21 Jul 2017 19:02:02 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 21-07-17 09:24, Daniel Vetter wrote: > Hi Greg&Hans, > > How are we going to handle this now? The refactor is deeply burried in > drm-misc, I guess you could cherry-pick the relevant patches over. But > that'll probably lead to more conflicts because git will get confused. > > Or you could just delete the set_busid hook in -staging, which renders > the driver unbisectable since it'll only work when merged together > with the drm trees. Removing the set_busid hook in staging (but only for -next, not for -linus) is fine with me. Regards, Hans