From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752105AbdLDUEn (ORCPT ); Mon, 4 Dec 2017 15:04:43 -0500 Received: from mail.kernel.org ([198.145.29.99]:50598 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751522AbdLDUEl (ORCPT ); Mon, 4 Dec 2017 15:04:41 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B721A21894 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=robh+dt@kernel.org X-Google-Smtp-Source: AGs4zMYpmRWDh9Jk+Q7qVEnIYz6xSM+XvTwnq9aV0FcWZlLWZXZIawZHB7+VSjHIyoUyfqCJp/ET+O1bANkBke9pQBE= MIME-Version: 1.0 In-Reply-To: <20171204191357.3211-3-atull@kernel.org> References: <20171204191357.3211-1-atull@kernel.org> <20171204191357.3211-3-atull@kernel.org> From: Rob Herring Date: Mon, 4 Dec 2017 14:04:19 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 2/2] of: dynamic: add overlay-allowed DT property To: Alan Tull Cc: Moritz Fischer , Frank Rowand , Pantelis Antoniou , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , linux-fpga@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 4, 2017 at 1:13 PM, Alan Tull wrote: > Allow DT nodes to be marked as valid targets for DT > overlays by the added "overlay-allowed" property. Why do you need a property for this? I'm not all that keen on putting this policy into the DT. It can change over time in the kernel. For example, as we define use cases that work, then we can loosen restrictions in the kernel. Rob