Received: by 10.223.164.221 with SMTP id h29csp4434034wrb; Thu, 19 Oct 2017 15:48:36 -0700 (PDT) X-Received: by 10.99.181.25 with SMTP id y25mr2586386pge.270.1508453316715; Thu, 19 Oct 2017 15:48:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1508453316; cv=none; d=google.com; s=arc-20160816; b=xq87WMBGd2Nev/H+H1sf6V1z1IBkRWihQiRzTO7qwxC73YA+O6z7WfrYtDqUHZ4aWd R9C5ICViMQG79JdO86YujsLJb1l9k+X8JWWsmDRP6/w4SRRhrGZmYUsBf1X9AtfxZlv3 CcUezhRXtu3AJNFdOxm/D+FIlCzJr9twshUtYXrlDSmgVBQcN9W61v15Lf3sbfuzUaPI M8js32Y/Vz4cB0cYgVqSMu9UT5WQ0F8Driw0/+wtKxuTR8j+oTAdEXgvKk4sz7cmYFKn LpbdKxOX10Xeov8uYld8tuGe5x1dEazw3TlKAX+xNqS0aH5SWm27sBmA+vD53WFD/uoG fJ5A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject:dkim-signature:arc-authentication-results; bh=ryiQQAZugnjI5H0AbZ9DxzkxxcdEx4oZLkjxHUo+vLA=; b=RQQ+9u916S8Iz0+PoWbx6LvuN2QSNgtWlJWW5UBwJ9NZyMMVXI4ml86CAfuz1JARpc fvc5tKbH/ySvz90q3b95hs9qr4QpUfM4eTwpnUYXIcjxVlVRzS/ix80zuWaJKJv3Mdz4 uzr2kgy5xQHDsoMy2Whl4bhGYv716yXwp+1FN7kmtyHL5JodycmzyCclutGMJ5GB2ElT JZwIvVqhusZ2GS30/vevvQDhSF1QCq0DDh7WeH5J2ppuwTlX7sa7yIqayczXvCIt+etH juQsZ1o0E/ub+RxfDWus9IFW8EcQ/yhV9/E7pB3sc6+BF7dZHRdAa/JKVU3D35IU/3i8 CZDA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=DpS/oYLY; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m69si4891768pfi.173.2017.10.19.15.48.22; Thu, 19 Oct 2017 15:48:36 -0700 (PDT) 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=pass header.i=@gmail.com header.s=20161025 header.b=DpS/oYLY; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752963AbdJSVq5 (ORCPT + 99 others); Thu, 19 Oct 2017 17:46:57 -0400 Received: from mail-pf0-f196.google.com ([209.85.192.196]:51632 "EHLO mail-pf0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752312AbdJSVqz (ORCPT ); Thu, 19 Oct 2017 17:46:55 -0400 Received: by mail-pf0-f196.google.com with SMTP id n14so7902723pfh.8; Thu, 19 Oct 2017 14:46:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=ryiQQAZugnjI5H0AbZ9DxzkxxcdEx4oZLkjxHUo+vLA=; b=DpS/oYLYjDyt3SznBH0O/ZV6GdArU02sUwTu642cjatU85LFQ5BEWa4Mpn3pb8zB1f pSv68vRZfAdmXJaUpvOpZjbE9jl40c0GgpzWsMQ2Rao3yoCk5xUak3lW2RyL4cuOC0Vm 1E+rCerxa4yS+i9lAWczlPY/Z2Dc3svXAKY4+eUl0Ph9MGFIfU0EzkYXiB55XHAH/qNf /qOHCnhdalWma2ZhgpLM7H7h/1xxlJjEaQikO/fCPrHbhBRBfKdadJ0uc+Jwm4MgRhQp 2MUUgvuW205dq21UqRa08DX2/kU90iFQcucXV8JqPTwI8ltmcbAoPTYbpzjMAyM/zlMB PlEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ryiQQAZugnjI5H0AbZ9DxzkxxcdEx4oZLkjxHUo+vLA=; b=ReKz21KEVViI1W4eSz44kyw7Fp4110t21/1nqQ4elx7YP2GiCmhUqzUkgoxaChhByt 0VK0mVHUYNf32rAcn+n+fKXTDWYn5uPS9eFPJfJlrbAM4XeMuq8kDgUnfVenDNYTx8eS sxnxMfrYymbc3FTcfpQY6rtT87ur3H0IVIfxCw295q+9+edh0UCUpP9NYtqmSg/ynC+Z lk8SnBVBzU2C/maJ+avyd/EtGE7GzHsPIdIUGL/qcZuEnYS9TAqj66/AFU7iBJF79FJC EEHGJGZpkzhULWiLxopSNosstqpKyfb9ddgkMEi9nuCvOha0dvKWw3hSkhQxdAXO+1nU dXKQ== X-Gm-Message-State: AMCzsaUmUI7zPBybxTS3wD+PGhhCxd8R7S4oGJn38wi3vv6MrveXYgvY 0Mr/VnkSjZc3QPifnXtEPvY= X-Google-Smtp-Source: ABhQp+QM6bVqDfRaQiSfq8vR/WzAK3JRpxerdsdK1h7EjPK7icrt9GevChL0xcCqxQiqo2mm/HMLWw== X-Received: by 10.99.63.199 with SMTP id m190mr2494973pga.187.1508449615238; Thu, 19 Oct 2017 14:46:55 -0700 (PDT) Received: from [192.168.1.46] (c-73-93-215-6.hsd1.ca.comcast.net. [73.93.215.6]) by smtp.gmail.com with ESMTPSA id 19sm28076753pfj.154.2017.10.19.14.46.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Oct 2017 14:46:54 -0700 (PDT) Subject: Re: [PATCH v2 5/5] of/fdt: only store the device node basename in full_name To: Moritz Fischer , Pantelis Antoniou References: <20170821151651.25096-1-robh@kernel.org> <20170821151651.25096-6-robh@kernel.org> <59E69786.2030406@gmail.com> <1508341985.25643.12.camel@hp800z> <4393AFA4-620F-4C21-995D-A9806DAE1990@konsulko.com> <20171019200615.GA10743@tyrael.ni.corp.natinst.com> Cc: Rob Herring , Alan Tull , "devicetree@vger.kernel.org" , Michael Ellerman , linuxppc-dev , linux-kernel , Benjamin Herrenschmidt , Paul Mackerras , David Laight , linux-fpga@vger.kernel.org From: Frank Rowand Message-ID: <59E91D4D.8000200@gmail.com> Date: Thu, 19 Oct 2017 14:46:53 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: <20171019200615.GA10743@tyrael.ni.corp.natinst.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/19/17 13:06, Moritz Fischer wrote: < snip > > We also have plenty of code that is just not aware of overlays, and > assumes certain parts of the tree to stay static. I would state that somewhat differently. :-) There is very little code that is aware of overlays, and most code assumes the device tree does not change after early boot. This is one of the areas where the creation of overlays needs to be done with care. > I ran into that issue when I tried to add thermal zones via an overlay, > I've been investigating how to fix the thermal framework to work with > overlays since then and have some partially working code. > Currently the thermal framework parses the thermal-zones node at boot, > and assumes this stays static. This breaks with overlays. > > I agree we eventually need to fix the parts that break when we use > overlays. From 1581720900578157582@xxx Thu Oct 19 20:56:38 +0000 2017 X-GM-THRID: 1576354368386704057 X-Gmail-Labels: Inbox,Category Forums