From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 26157C282CA for ; Tue, 12 Feb 2019 07:28:28 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EB41A2186A for ; Tue, 12 Feb 2019 07:28:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1549956508; bh=+JfyTDTQ7p5u7zNst0aiMSzCg/K44ftDsfjYwEBGeaU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=10BdFWABLI0mmTxE74SXENtd9EAJDLSH00yhOw6CF8pfuBia8WbAH3WYfNGEz1mON L3MXUsPWpps19YN9vnOYkYAsmyMJ9Hnija1TURR0MoHSbAkFbJi4AM5F1GDNP0ewZz k8yUcuXDO0m9gKgsouTXOd4muLDwjALKgC3o/BvM= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727889AbfBLH20 (ORCPT ); Tue, 12 Feb 2019 02:28:26 -0500 Received: from mail.kernel.org ([198.145.29.99]:57890 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725916AbfBLH20 (ORCPT ); Tue, 12 Feb 2019 02:28:26 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 833762083B; Tue, 12 Feb 2019 07:28:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1549956505; bh=+JfyTDTQ7p5u7zNst0aiMSzCg/K44ftDsfjYwEBGeaU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=g4dWgYtFpYNEJ0Cf5T6rgUftz5dYoCcYdaZb+yHv1CfvTi2rCyKtMNDWHUBQxad1X 0WPnA3dVarOMGn7/L8MRo/Wvm2oRsbsuIoOvGUzx3rVnZiP7nQRimRM2d0TG7KmV4F GeIpIxDZZLYtvqaOHWXbXJ/mZNBSxS7CjKh1QxkQ= Date: Tue, 12 Feb 2019 08:28:21 +0100 From: Greg Kroah-Hartman To: Alan Tull Cc: Frank Rowand , Rob Herring , Pantelis Antoniou , Michael Ellerman , Benjamin Herrenschmidt , Paul Mackerras , Moritz Fischer , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , linuxppc-dev , linux-fpga@vger.kernel.org Subject: Re: [GIT PULL] of: overlay: validation checks, subsequent fixes for v20 -- correction: v4.20 Message-ID: <20190212072821.GA2940@kroah.com> References: <262419e9-5c9f-1193-f119-33f373d81e43@gmail.com> <20190211191341.GA13134@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.3 (2019-02-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 11, 2019 at 02:43:48PM -0600, Alan Tull wrote: > On Mon, Feb 11, 2019 at 1:13 PM Greg Kroah-Hartman > wrote: > > > > On Mon, Feb 11, 2019 at 12:41:40PM -0600, Alan Tull wrote: > > > On Fri, Nov 9, 2018 at 12:58 AM Frank Rowand wrote: > > > > > > What LTSI's are these patches likely to end up in? Just to be clear, > > > I'm not pushing for any specific answer, I just want to know what to > > > expect. > > > > I have no idea what you are asking here. > > > > What patches? > > I probably should have asked my question *below* the pertinent context > of the the 17 patches listed in the pull request, which was: > > > of: overlay: add tests to validate kfrees from overlay removal > > of: overlay: add missing of_node_put() after add new node to changeset > > of: overlay: add missing of_node_get() in __of_attach_node_sysfs > > powerpc/pseries: add of_node_put() in dlpar_detach_node() > > of: overlay: use prop add changeset entry for property in new nodes > > of: overlay: do not duplicate properties from overlay for new nodes > > of: overlay: reorder fields in struct fragment > > of: overlay: validate overlay properties #address-cells and #size-cells > > of: overlay: make all pr_debug() and pr_err() messages unique > > of: overlay: test case of two fragments adding same node > > of: overlay: check prevents multiple fragments add or delete same node > > of: overlay: check prevents multiple fragments touching same property > > of: unittest: remove unused of_unittest_apply_overlay() argument > > of: overlay: set node fields from properties when add new overlay node > > of: unittest: allow base devicetree to have symbol metadata > > of: unittest: find overlays[] entry by name instead of index > > of: unittest: initialize args before calling of_*parse_*() > > > What is "LTSI's"? > > I have recently seen some of devicetree patches being picked up for > the 4.20 stable-queue. That seemed to suggest that some, but not all > of these will end up in the next LTS release. If the git commit has the "cc: stable@" marking in it, yes, it will be picked up. Without the actual git ids, it's hard to know what did, and what did not, get backported :) > Also I was wondering if any of this is likely to get backported to > LTSI-4.14. Note, "LTSI" and "LTS" are two different things. "LTSI" is a project run by some LF member companies, and "LTS" are the normal long term kernels that I release on kernel.org. They have vastly different requirements for inclusion in them. If you have questions about LTSI, I recommend go asking on their mailing list. As for showing up in the 4.14 "LTS" kernel, again, I need git commit ids to know for sure. Also, as these are now in Linus's tree, you should be able to look at the stable releases yourself to see if they are present there, right? thanks, greg k-h