Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp873545ybi; Fri, 31 May 2019 10:06:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqxFL+JK8BmiNiZ5hn4RWKSoAD7i03PUVTkPvln0shzYWs0acdQXA8dpuMnIkQOgDl085No9 X-Received: by 2002:a17:90a:9b8b:: with SMTP id g11mr10703802pjp.95.1559322383328; Fri, 31 May 2019 10:06:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559322383; cv=none; d=google.com; s=arc-20160816; b=xe0eM9yyi093qKapNUB4xV210pD9j+FE3TRHH3ckGIEE8YmFh72F4F2pCTRXGDkJuu N5W/rZJFWIEVvaG33R97t0kfz4ntFhQZsiVF7i81Jd897N7AsOFDvMttKORRjVTdU5WJ H8I0FLEgzJIVIrTuVry6GpCO8K8GXF2js9BZaT2o6SNI57wBEE2/UNfjKn122b+46Ykz wwNNYr/xylK7co1IMFyU64FM8iPMTiHw8p2bbq5n0MHkQWuqJ/6E5f6341YJeH/Q/vN3 qLVWjtIPC7zAsZcWd1x2gkaU+ovPrXiHJQF1Fcua2C0TcrLKYjkQZhvsIXz83koiA+ga SMnQ== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:openpgp:from:references:cc:to:subject; bh=5Knli4y1MY3AlBhhVC1vOuM6xAbeLK7fOUPS+vTmFgI=; b=McP91svNku7U1nANYMMODVvjcsh9rnUeK2FqQ/9HX/uTqw3fY/NwktgkDoIdee3ZT3 GAvHV59UvQCB8ziJIvJuZlv3ILzjxtOOtucZJIV9rcmVBd2kAoredLR4qk+/nTgVnHPz DRi2Nk7zNr4MqygLKvH06bJqudm95n3BSvG55wOF9tNto2U4Z7PlfvUX50Dp5ZGy2dMf D9IyfN+EK1iVQHsl6JTiLh5bHYZ/F2g6kNbbvdojnqP+QP9VGS6C0RkT4SK0S4E60mJG ORj3WaszcL1HrVYRKVBrBkVLF4W3HCp5lpvkquq+RMJZHlSVYalScGoclRi2ZySje7aA jccQ== ARC-Authentication-Results: i=1; mx.google.com; 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 d197si6260416pga.110.2019.05.31.10.06.05; Fri, 31 May 2019 10:06:23 -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; 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 S1727005AbfEaRDv (ORCPT + 99 others); Fri, 31 May 2019 13:03:51 -0400 Received: from mx2.suse.de ([195.135.220.15]:60434 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726678AbfEaRDu (ORCPT ); Fri, 31 May 2019 13:03:50 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 91664ACC4; Fri, 31 May 2019 17:03:49 +0000 (UTC) Subject: Re: [PATCH v3 0/6] Prerequisites for NXP LS104xA SMMU enablement To: Laurentiu Tudor Cc: "netdev@vger.kernel.org" , Madalin-cristian Bucur , Roy Pledge , Camelia Alexandra Groza , Leo Li , "linux-kernel@vger.kernel.org" , "jocke@infinera.com" , "iommu@lists.linux-foundation.org" , "linuxppc-dev@lists.ozlabs.org" , "davem@davemloft.net" , "linux-arm-kernel@lists.infradead.org" , Mian Yousaf Kaukab References: <20190530141951.6704-1-laurentiu.tudor@nxp.com> From: =?UTF-8?Q?Andreas_F=c3=a4rber?= Openpgp: preference=signencrypt Organization: SUSE Linux GmbH Message-ID: <19cc3230-33b0-e465-6317-590780b33efa@suse.de> Date: Fri, 31 May 2019 19:03:48 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Laurentiu, Am 31.05.19 um 18:46 schrieb Laurentiu Tudor: >> -----Original Message----- >> From: Andreas Färber >> Sent: Friday, May 31, 2019 7:15 PM >> >> Hi Laurentiu, >> >> Am 30.05.19 um 16:19 schrieb laurentiu.tudor@nxp.com: >>> This patch series contains several fixes in preparation for SMMU >>> support on NXP LS1043A and LS1046A chips. Once these get picked up, >>> I'll submit the actual SMMU enablement patches consisting in the >>> required device tree changes. >> >> Have you thought through what will happen if this patch ordering is not >> preserved? In particular, a user installing a future U-Boot update with >> the DTB bits but booting a stable kernel without this patch series - >> wouldn't that regress dpaa then for our customers? >> > > These are fixes for issues that popped out after enabling SMMU. > I do not expect them to break anything. That was not my question! You're missing my point: All your patches are lacking a Fixes header in their commit message, for backporting them, to avoid _your DT patches_ breaking the driver on stable branches! Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg)