Received: by 10.223.164.202 with SMTP id h10csp3499996wrb; Sun, 19 Nov 2017 23:42:29 -0800 (PST) X-Google-Smtp-Source: AGs4zMarZ+PGLgkpDIYl7HeXfpD3tCclU+nfsSBmq/vR/KTfxE9R7WSdCwPd/LbGSCBFojmPI697 X-Received: by 10.159.218.152 with SMTP id w24mr10814262plp.336.1511163748945; Sun, 19 Nov 2017 23:42:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1511163748; cv=none; d=google.com; s=arc-20160816; b=DvMJr3/P+/QUqxJWwyg2wbT0oTIqknD49Aa/umvKVMOcziKkG/WhM3rOpZc37DpV6t FvqgSNmRgIhrsNhoXtNsf5uCL8HwEoHSQsZxpf7/zI1gowyeav4mZn0ObIMGD4Wni9Cd sewdOUB/znjYD93Bt1OlqH0iemW/DNz0KTPMAGNHaCrEHft+XwhLGsMOjjQEyT27Htaz MuAs4q1n7Vlsa5N4HUoSyTWaFDgmNsnK4b1GWU5xkqEbNyC0nlx1HbfnJ6lHszYz1vMV ssalsUXh170AhH5KoorjgCbPMWpYWfQTVeCBibbxaLaPi0nrDS7lFjRQYE8ZlI1amElA naig== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature :arc-authentication-results; bh=w5V3ERRy4QUfhRdtWOH4OfZRQvrMBuo2PlBmXzWFw4I=; b=P/ndXGYumQEOevzdiUfc+hJPUfWiQCiUC7Q0ecoAT2ODO6nTyCaxhfBvZlBRP1MN2M dYkqrtFqYh+k4xVeyWyempk+HiiBSnh1ABlY1mykYBTMscP/+7xeZpeEZS6mRjIsjXHO caBqUXhdKq3uLb99xcz7WvPZrDo9ZjkvcM94oVEyewxOHZ2QmJyJA2hNOb/VC0zSCKdd Hp8zhoJtjVngGd2LARaf/5sTOKeR2FVxRBb6Pv82/tZRiXerZypbPnifhXFjW5CHkJF9 nYw+hxnhJv3n3AOuRDyzQ9xabQd4g9dBxvtnG+vpB2NoeDofEBDxQ629fEAsora/IY5/ 4/Bg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@ffwll.ch header.s=google header.b=IWM3GDpp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x4si7402467plw.539.2017.11.19.23.42.18; Sun, 19 Nov 2017 23:42:28 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@ffwll.ch header.s=google header.b=IWM3GDpp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751092AbdKTHlg (ORCPT + 68 others); Mon, 20 Nov 2017 02:41:36 -0500 Received: from mail-wm0-f54.google.com ([74.125.82.54]:36395 "EHLO mail-wm0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750962AbdKTHle (ORCPT ); Mon, 20 Nov 2017 02:41:34 -0500 Received: by mail-wm0-f54.google.com with SMTP id r68so16640920wmr.1 for ; Sun, 19 Nov 2017 23:41:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=w5V3ERRy4QUfhRdtWOH4OfZRQvrMBuo2PlBmXzWFw4I=; b=IWM3GDppIaq00wG6gkTLgGexvb8ziUV8Mpdx8gh52QR0JK1jcKDWDMF+6wKgSZXjVR QqLTIBN+NviKOoOpBx8QkHW810sTlEw3TGoKQVS2iWa4fP/XnMPtrVX8N9tXZvHHYZ2r 0jovBQnuXx1MVKsuTYA0K8KeZ0Eb8dwOnUuYM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=w5V3ERRy4QUfhRdtWOH4OfZRQvrMBuo2PlBmXzWFw4I=; b=qhm4uNirL40f5ctgSWSrutFQpxqhItnmxhiOu8Rda9AyGG70PlnpRzVcHeYcekzzm5 XJTA2cRXmY7Ab+P7DwB0eILWG9SnI8PVgiLcQP5JMdGzTDmoIAD34QhU8fkq3yPZcX7q VtWszbOC9IJatXBqoZSq+AY0UZTdIevmRCvzpDHypq/Gp+G+rlJg6665H3OOlzBhMbz3 9mV5XD2OUNuY97ujlAIcgP9sA10+sF+yAcpyQVKvnTjRIQ7YMxoX58ChjavRn81WxuQ8 LWJLnj1eyOGQYFB5uI+7IxG7wiyzhp1MKP0PSQq9bytFIqjdHH04/hFHZdW5Y50OQ0YH lEkw== X-Gm-Message-State: AJaThX4jPdDqK92bDUyqRjKq4gtZfprajf+Vm2wU42yrcwxIbdzDejMb rLiisPZR3a98alz+QLQpnFzaHg== X-Received: by 10.80.212.34 with SMTP id t34mr15523112edh.22.1511163692755; Sun, 19 Nov 2017 23:41:32 -0800 (PST) Received: from phenom.ffwll.local ([2a02:168:5635:0:39d2:f87e:2033:9f6]) by smtp.gmail.com with ESMTPSA id t23sm7948457edb.70.2017.11.19.23.41.31 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 19 Nov 2017 23:41:32 -0800 (PST) Date: Mon, 20 Nov 2017 08:41:30 +0100 From: Daniel Vetter To: Jyri Sarha Cc: Frank Rowand , Stephen Rothwell , Rob Herring , Rob Herring , ave Airlie , DRI , Mark Brown , Frank Rowand , Stephen Boyd , Linux-Next Mailing List , Linux Kernel Mailing List , Daniel Vetter , "Valkeinen, Tomi" Subject: Re: linux-next: manual merge of the devicetree tree with the drm tree Message-ID: <20171120074129.sy6gyfaqhqbch4hy@phenom.ffwll.local> Mail-Followup-To: Jyri Sarha , Frank Rowand , Stephen Rothwell , Rob Herring , Rob Herring , ave Airlie , DRI , Mark Brown , Frank Rowand , Stephen Boyd , Linux-Next Mailing List , Linux Kernel Mailing List , "Valkeinen, Tomi" References: <20171030203756.35brom4ulrbgqesv@sirena.co.uk> <20171113165831.19ebc9fa@canb.auug.org.au> <153e4593-2ebb-c091-49c8-b8d44d5caeb5@ti.com> <917c5115-3d36-92bd-2713-5a6119fc82ca@gmail.com> <6e7a5a3e-c5a9-7069-74bc-06037761af93@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6e7a5a3e-c5a9-7069-74bc-06037761af93@ti.com> X-Operating-System: Linux phenom 4.9.0-3-amd64 User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 13, 2017 at 09:51:29PM +0200, Jyri Sarha wrote: > On 11/13/17 20:43, Frank Rowand wrote: > > Hi Jyri, > > > > On 11/13/17 07:40, Jyri Sarha wrote: > >> On 11/13/17 07:58, Stephen Rothwell wrote: > >>> Hi all, > >>> > >>> On Mon, 30 Oct 2017 20:37:56 +0000 Mark Brown wrote: > >>>> Today's linux-next merge of the devicetree tree got a conflict in: > >>>> > >>>> drivers/gpu/drm/tilcdc/tilcdc_slave_compat.c > >>>> > >>>> between commit: > >>>> > >>>> 44cd3939c111b7 ("drm/tilcdc: Remove redundant OF_DETACHED flag setting") > >>>> > >>>> from the drm tree and commit: > >>>> > >>>> f948d6d8b792bb ("of: overlay: avoid race condition between applying multiple overlays") > >>>> > >>>> from the devicetree tree. > >>>> > >>>> I fixed it up (see below) and can carry the fix as necessary. This > >>>> is now fixed as far as linux-next is concerned, but any non trivial > >>>> conflicts should be mentioned to your upstream maintainer when your tree > >>>> is submitted for merging. You may also want to consider cooperating > >>>> with the maintainer of the conflicting tree to minimise any particularly > >>>> complex conflicts. > >>>> > >>>> diff --cc drivers/gpu/drm/tilcdc/tilcdc_slave_compat.c > >>>> index 482299a6f3b0,54025af534d4..000000000000 > >>>> --- a/drivers/gpu/drm/tilcdc/tilcdc_slave_compat.c > >>>> +++ b/drivers/gpu/drm/tilcdc/tilcdc_slave_compat.c > >>>> @@@ -163,12 -162,8 +162,6 @@@ static struct device_node * __init tilc > >>>> return NULL; > >>>> } > >>>> > >>>> - ret = of_resolve_phandles(overlay); > >>>> - if (ret) { > >>>> - pr_err("%s: Failed to resolve phandles: %d\n", __func__, ret); > >>>> - return NULL; > >>>> - } > >>>> - of_node_set_flag(overlay, OF_DETACHED); > >>>> -- > >>>> return overlay; > >>>> } > >>>> > >>> Just a reminder that this conflict still exists. > >>> > >> After some consideration, I think we can drop the dts backward > >> compatibility code from drm/tilcdc. It seems that it is causing a lot of > >> trouble and I do not even know if anybody uses it anymore. Here is a > >> patch for dropping it: > >> > >> https://lists.freedesktop.org/archives/dri-devel/2017-November/157394.html > >> > >> I did not plan to merge it before v4.16, but if this is a bigger problem > >> I can push is right now for v4.15. > >> > >> Best regards, > >> Jyri > >> > > The dropping patch is much appreciated. > > > > It would make life easier for me if the patch gets into v4.15-rc. > > Dave, Daniel? Would you take this late addition to v4.15 still, if I > would send a pull request now? > > The patch is pretty much orthogonal to the rest of drm as it is only > dealing with device tree stuff. Seems like a reasonable thing to include in the merge window -fixes pull Dave usually does, just make sure all the acks are recorded. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch From 1583981798573695930@xxx Mon Nov 13 19:52:38 +0000 2017 X-GM-THRID: 1582716362758856630 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread