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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 751C0C433EF for ; Tue, 17 May 2022 07:18:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235840AbiEQHSQ convert rfc822-to-8bit (ORCPT ); Tue, 17 May 2022 03:18:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57074 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231211AbiEQHSP (ORCPT ); Tue, 17 May 2022 03:18:15 -0400 Received: from szxga02-in.huawei.com (szxga02-in.huawei.com [45.249.212.188]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 11D2B473A9 for ; Tue, 17 May 2022 00:18:13 -0700 (PDT) Received: from dggpemm500022.china.huawei.com (unknown [172.30.72.54]) by szxga02-in.huawei.com (SkyGuard) with ESMTP id 4L2S9v2s7pzhZWN; Tue, 17 May 2022 15:17:23 +0800 (CST) Received: from dggpemm500006.china.huawei.com (7.185.36.236) by dggpemm500022.china.huawei.com (7.185.36.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 17 May 2022 15:18:11 +0800 Received: from lhreml710-chm.china.huawei.com (10.201.108.61) by dggpemm500006.china.huawei.com (7.185.36.236) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 17 May 2022 15:18:10 +0800 Received: from lhreml710-chm.china.huawei.com ([169.254.81.184]) by lhreml710-chm.china.huawei.com ([169.254.81.184]) with mapi id 15.01.2375.024; Tue, 17 May 2022 08:18:07 +0100 From: Shameerali Kolothum Thodi To: Lorenzo Pieralisi , Robin Murphy , "rafael@kernel.org" , "joro@8bytes.org" CC: "Guohanjun (Hanjun Guo)" , "linux-arm-kernel@lists.infradead.org" , "linux-acpi@vger.kernel.org" , "iommu@lists.linux-foundation.org" , Linuxarm , "will@kernel.org" , wanghuiqiang , "steven.price@arm.com" , "Sami.Mujawar@arm.com" , "jon@solid-run.com" , "eric.auger@redhat.com" , "laurentiu.tudor@nxp.com" , "hch@infradead.org" Subject: RE: [PATCH v12 0/9] ACPI/IORT: Support for IORT RMR node Thread-Topic: [PATCH v12 0/9] ACPI/IORT: Support for IORT RMR node Thread-Index: AQHYXwu3gTgIMyz0zUiu6Dja1BmGsa0PbqaAgAhOLiD///4qAIAE064AgAYtdiA= Date: Tue, 17 May 2022 07:18:07 +0000 Message-ID: <0481f110d060413aaf32228b0be68ef2@huawei.com> References: <20220503163330.509-1-shameerali.kolothum.thodi@huawei.com> <2234ad60-c49f-8c72-616c-dfa5300354ef@huawei.com> <8e4f012717e34195a53cb73f8ce28627@huawei.com> <5c8ae673-f8e3-0ed3-e62d-d445913b012c@arm.com> <20220513094940.GA23371@lpieralisi> In-Reply-To: <20220513094940.GA23371@lpieralisi> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.202.227.178] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org > -----Original Message----- > From: Lorenzo Pieralisi [mailto:lorenzo.pieralisi@arm.com] > Sent: 13 May 2022 10:50 > To: Robin Murphy ; Shameerali Kolothum Thodi > ; rafael@kernel.org; > joro@8bytes.org > Cc: Shameerali Kolothum Thodi ; > Guohanjun (Hanjun Guo) ; > linux-arm-kernel@lists.infradead.org; linux-acpi@vger.kernel.org; > iommu@lists.linux-foundation.org; Linuxarm ; > will@kernel.org; wanghuiqiang ; > steven.price@arm.com; Sami.Mujawar@arm.com; jon@solid-run.com; > eric.auger@redhat.com; laurentiu.tudor@nxp.com; hch@infradead.org > Subject: Re: [PATCH v12 0/9] ACPI/IORT: Support for IORT RMR node > > [with Christoph's correct email address] > > On Tue, May 10, 2022 at 09:07:00AM +0100, Robin Murphy wrote: > > On 2022-05-10 08:23, Shameerali Kolothum Thodi wrote: > > > Hi Joerg/Robin, > > > > > > I think this series is now ready to be merged. Could you please let > > > me know if there is anything missing. > > > > Fine by me - these patches have had enough review and testing now that > > even if anything else did come up, I think it would be better done as > > follow-up work on the merged code. > > Given the ACPICA dependency I believe it is best for this series > to go via the ACPI tree, right ? > > I assume there are all the required ACKs for that to happen. The SMMUv3/SMMU related changes (patches 6 - 9) still doesn't have explicit ACK from maintainers other than the go ahead above from Robin. Just thought of highlighting it as not sure that will be an issue or not. Thanks, Shameer