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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id DB5C9C47DD9 for ; Fri, 23 Feb 2024 02:08:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=3PnpbZeSbASu0UWP8u4rwAcsnmep4j75jWgTQigQhwA=; b=Ux4jPU6XAYko2Q 12g7rNoCK3rk5tcDBVQPR/v7Yk+MnUZLgqIPc3+C4jfJYRjFuAsaIIF15h5uDGmyB/pi7sTwrFkV4 5WIjNERV1+N9+HLt8xHySeXDj4QRCFB+AEmhZxyAk6GdBEjuX78ZUUnUYcz/azWO8V07cA8pSPnHi Aoy11ccmAEw9IA2T8CmJf+QoiXo7TtMRxXPQxFZTnDmCGrzb6TykcyVnMhob8ganCSuCYdVpI/TNC 1MzXaTwybps8jqA9v1ZFmv4P4/BaaT25IA6zKXc1S7YoqureV5KddaoZVAKZuhx3Oa0fWS9A4eyYF YARLvK7Cw2GVi2QWiRhw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rdKzJ-00000007VY5-1FYI; Fri, 23 Feb 2024 02:08:33 +0000 Received: from mail-177132.yeah.net ([123.58.177.132]) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rdKzD-00000007VWj-27r6 for linux-arm-kernel@lists.infradead.org; Fri, 23 Feb 2024 02:08:31 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yeah.net; s=s110527; h=Date:From:Subject:Message-ID:MIME-Version: Content-Type; bh=lCE9TnObaj9CSGcGHs9TSjrZX9bW094ZFtuDVElRcVg=; b=pc6wQcWDigcnsqIJFEhtNoozHHMXPVOdQ9QGTxZKVuJ/+cl3LAWv8I/78CXOqM eYRGgx06AHlQE3Ed6kk/2MSw3jCupZWDo/E5dqrsXZTqamzd7dZvUSr/WWsWiE1F VSWTtOzX9sBEjDRmM0EOCXjwMMg6mEjuRKjxQKXDTFn3I= Received: from dragon (unknown [183.213.196.200]) by smtp2 (Coremail) with SMTP id C1UQrADHrojr_ddlCaQsBA--.4847S3; Fri, 23 Feb 2024 10:07:40 +0800 (CST) Date: Fri, 23 Feb 2024 10:07:39 +0800 From: Shawn Guo To: Jakub Kicinski Cc: Frank Li , Ulf Hansson , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , Fabio Estevam , NXP Linux Team , Wei Fang , Shenwei Wang , Clark Wang , "David S. Miller" , Eric Dumazet , Paolo Abeni , linux-mmc@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, imx@lists.linux.dev Subject: Re: [PATCH v2 0/4] Add 8qm SMMU information Message-ID: References: <20240201-8qm_smmu-v2-0-3d12a80201a3@nxp.com> <20240202110511.135d26b7@kernel.org> <20240206074151.577d33f1@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20240206074151.577d33f1@kernel.org> X-CM-TRANSID: C1UQrADHrojr_ddlCaQsBA--.4847S3 X-Coremail-Antispam: 1Uf129KBjDUn29KB7ZKAUJUUUU8529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UbIYCTnIWIevJa73UjIFyTuYvjxUcjg4DUUUU X-Originating-IP: [183.213.196.200] X-CM-SenderInfo: pvkd40hjxrjqh1hdxhhqhw/1tbiFQyNZV6Nm5-2UQAAsB X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240222_180829_722842_C6F6D71C X-CRM114-Status: GOOD ( 10.85 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Feb 06, 2024 at 07:41:51AM -0800, Jakub Kicinski wrote: > On Tue, 6 Feb 2024 18:50:51 +0800 Shawn Guo wrote: > > > Any preference on whether all these go via a platform tree, > > > or should we pick up the net patch to netdev? I guess taking > > > the DTB via netdev would be the usual way to handle this? > > > > No, it's not. Taking DTS changes through arch/platform tree is the > > usual way. > > I said DTB. If the DTB here means Device Tree Blob which is generated by DTC (Device Tree Compiler) taking DTS (Device Tree Source) as input, it's a build result and so neither of us could take. Shawn _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel