Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp12085957rwl; Tue, 3 Jan 2023 08:50:58 -0800 (PST) X-Google-Smtp-Source: AMrXdXtFSxT3FaLPmoNH5iMSwjXS3u+Rj73mhjUkBCuM7bfkCNOKyJ1Uby6WDIX1g7M+eujNDpHU X-Received: by 2002:aa7:90d4:0:b0:582:b8e0:bc54 with SMTP id k20-20020aa790d4000000b00582b8e0bc54mr2930081pfk.21.1672764657948; Tue, 03 Jan 2023 08:50:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672764657; cv=none; d=google.com; s=arc-20160816; b=pVa0SeNMmYgqxSYBdTSRSrLXLi29RFrp2PzM3dAI2YGOB7EG2Xp3KH48chPvMyr7O6 nReoJneQ28AjZAyjzmwtCIDP0Jd5eMtcuAbUm94q9DjGhvKcmD7KB2FDkQwCPCpN939K nq+3EilfRLu80bZJzy7pNY5Mhn+VO09EZ4mseLeg0Wz1DWpamtVtOwa6MOXIK79mYEoN WWBdMAZcjbrhJ+ShMYZw24GLW6M9lX8Tw8qXdMI7aBQI44k9V+qx9CvN+ryp9deeez46 lZ0SYZ3QpjheWOnCH6olg/AsC5cacC6jC+QQsu4XXIj7T+Qam9k2+YTPYkYSPUt85epm iPNQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id; bh=WU0dokbZJR7hGpUs28LPuEyaZMppFxtbY3wOwZuSs+U=; b=nCQQ786Ahp5YpUSiPh0jKiIGwevCm3LHOvNOEQ0L3QKFb6W3HycUEwm+QYwn5VR+7e t8k+LoFBIR70WgUwP0uZh9kjasht2c/uJ14ShwHs85orvf0+znQ0VC8PGbkbR6hJV4iQ BPXu+Whe2jVIWTMgVginR8Un4elXuOOSrvtiNYJCGR/N9joceCsArk6ey+rJ4thK9z2M 8yp14gh/aFnxRHz9hcDacdelMujQgqfw0pSZf1Hm41nNli1YWBkQem/y1fZjLCzoc58T WoAbdb7nnXV69KfbL0Wt5tUnT+awQC3CyNoKxSHC4HYgZTNQ5vRgyonoRf+XHaNTPZlT 9pjQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j63-20020a625542000000b0057a7b003c82si31500380pfb.219.2023.01.03.08.50.50; Tue, 03 Jan 2023 08:50:57 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233648AbjACQkU (ORCPT + 61 others); Tue, 3 Jan 2023 11:40:20 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57922 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238136AbjACQkL (ORCPT ); Tue, 3 Jan 2023 11:40:11 -0500 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 26DFADFF5 for ; Tue, 3 Jan 2023 08:40:10 -0800 (PST) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 819861516; Tue, 3 Jan 2023 08:40:51 -0800 (PST) Received: from [10.1.196.40] (e121345-lin.cambridge.arm.com [10.1.196.40]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 804AE3F71A; Tue, 3 Jan 2023 08:40:07 -0800 (PST) Message-ID: <832f3200-77ac-1ee0-e1b5-5f56353cba36@arm.com> Date: Tue, 3 Jan 2023 16:39:59 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: [PATCH v2 2/3] iommu/sound: Use component_match_add_of helper Content-Language: en-GB To: Maxime Ripard Cc: Sean Anderson , David Airlie , Daniel Vetter , Maarten Lankhorst , Thomas Zimmermann , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Mark Brown , Jaroslav Kysela , Joerg Roedel , Liam Girdwood , Matthias Brugger , Takashi Iwai , Will Deacon , Yong Wu , alsa-devel@alsa-project.org, iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org References: <20221222233759.1934852-1-sean.anderson@seco.com> <20221222233759.1934852-3-sean.anderson@seco.com> <7897d4a6-bf43-becd-3437-7a254f38f6be@arm.com> <20230103161550.4tui3ihl65olvkd7@houat> From: Robin Murphy In-Reply-To: <20230103161550.4tui3ihl65olvkd7@houat> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.3 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/01/2023 4:15 pm, Maxime Ripard wrote: > Hi Robin, > > On Tue, Jan 03, 2023 at 01:01:07PM +0000, Robin Murphy wrote: >> Hi Sean, >> >> On 22/12/2022 11:37 pm, Sean Anderson wrote: >>> Convert users of component_match_add_release with component_release_of >>> and component_compare_of to component_match_add_of. >>> >>> Signed-off-by: Sean Anderson >>> Acked-by: Mark Brown >>> --- >>> >>> Changes in v2: >>> - Split off from helper addition >>> >>> drivers/iommu/mtk_iommu.c | 3 +-- >>> drivers/iommu/mtk_iommu_v1.c | 3 +-- >>> sound/soc/codecs/wcd938x.c | 6 ++---- >>> 3 files changed, 4 insertions(+), 8 deletions(-) >>> >>> diff --git a/drivers/iommu/mtk_iommu.c b/drivers/iommu/mtk_iommu.c >>> index 2ab2ecfe01f8..483b7a9e4410 100644 >>> --- a/drivers/iommu/mtk_iommu.c >>> +++ b/drivers/iommu/mtk_iommu.c >>> @@ -1079,8 +1079,7 @@ static int mtk_iommu_mm_dts_parse(struct device *dev, struct component_match **m >>> } >>> data->larb_imu[id].dev = &plarbdev->dev; >>> - component_match_add_release(dev, match, component_release_of, >>> - component_compare_of, larbnode); >>> + component_match_add_of(dev, match, larbnode); >> >> I've long since given up trying to make sense of how the DRM tree works, but >> the conflicting change is definitely already in mainline: >> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=b5765a1b44bea9dfcae69c53ffeb4c689d0922a7 > > As far as I can see, that patch doesn't affect DRM at all, and the > commit you pointed to doesn't either, nor has it been merged through the > DRM tree. Right it doesn't affect DRM, and was merged via the IOMMU tree, but it does affect *this* patch, which Sean has based on a drm-next branch that seemingly still wasn't up to date with 6.2-rc1 at the time. Since v2 had already been posted, it seemed like a bright idea to comment here to clarify that it was still relevant, rather than bumping the old thread to reply directly. Apologies for any confusion. In practical terms I think it's merely a case of dropping this hunk; the other one in mtk_iommu_v1.c looks fine to me. Cheers, Robin. > Can you expand a bit on how we're involved in this, what we should > clarify or help with? > > Maxime