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 3EB4EC43458 for ; Thu, 9 Jul 2026 10:03:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=+ak7g+bnNvjs6BgBEr/Bs7DjjcW1VaCyUfDXvUXZ24I=; b=myPfxkg1Ig3Tcv5Q0mN2tkjF2k VvTtcWHutEACbjh1ivOOtaR8Z7Ob/6YJ0aJ4ACZjypb9S4Ar5qIYOHtAdktKbyLMi/JkQ2B+LWapa NRHWPdMuaxZujt0faUVSv6xy2Oi2ZpEieLVOxcL1SSTCH9pRvqLQ0QYMGV6rSZ8Qy+urRFyhTGlVc GPxvmzQae/pZh2uMTuMP+gBd+mV+wlQOkmC5ZpmKl0DU90id2UrJt8ZCR+L5rwgBH8UTKpBW7dEWO YvXU+keyi790rJZxUEJYj/UpKx00th1ctVTroEnUNVsYBfSnzE4tKfgcyLY3c5tqBCQjrZwUTpisZ 6dYkAGOA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1whlbE-00000001rNg-0m0X; Thu, 09 Jul 2026 10:03:20 +0000 Received: from tor.source.kernel.org ([172.105.4.254]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1whlb8-00000001rMB-44c3; Thu, 09 Jul 2026 10:03:15 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id 2DD1F600C3; Thu, 9 Jul 2026 10:03:14 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id E731C1F000E9; Thu, 9 Jul 2026 10:03:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1783591393; bh=+ak7g+bnNvjs6BgBEr/Bs7DjjcW1VaCyUfDXvUXZ24I=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=gbAbOtT3xXk/mcJ1eT0tQ/7wTMH+HHidCthinZFuF3zrSj6VpvqufBIjNyy9WdhAb iXzvhaQZT0jUbVwaBDmQjSY0uw7WRKsLuAuN6zNSfBks8I9jTszW8LBQPKMLgNwl9N 2icoPJfvY1GX+9ejjz7LAV9bnkUnRhLJ2u+v76Sb5dGdp4iMqMudghZdRDXMSNi3iW ttqmCKfFDH3pKqRy67YcIy1H1kaCh8ZA/R/Dt/K4R3ivi4aYKVyx0JRQBU9YbXskog bkxfi5V3N1ohep4Cg6imr9Uc3pGgloh4rsV6NBuLw25Z6lX9IZ/PRw2VbyILse1DhH 6ATkVUShF/UWg== Date: Thu, 9 Jul 2026 11:03:08 +0100 From: Lee Jones To: Roman Vivchar Cc: Jonathan Cameron , David Lechner , Nuno =?iso-8859-1?Q?S=E1?= , Andy Shevchenko , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Matthias Brugger , AngeloGioacchino Del Regno , linux-iio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, Ben Grisdale Subject: Re: [PATCH v4 3/4] mfd: mt6397-core: add mt6323 AUXADC support Message-ID: <20260709100308.GD2045740@google.com> References: <20260623-mt6323-adc-v4-0-299680ad3194@protonmail.com> <20260623-mt6323-adc-v4-3-299680ad3194@protonmail.com> <20260708211056.GB1727174@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: linux-mediatek@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "Linux-mediatek" Errors-To: linux-mediatek-bounces+linux-mediatek=archiver.kernel.org@lists.infradead.org On Thu, 09 Jul 2026, Roman Vivchar wrote: > Hi Lee, > > +Jonathan > > On Thursday, July 9th, 2026 at 12:11 AM, Lee Jones wrote: > > > On Tue, 23 Jun 2026, Roman Vivchar via B4 Relay wrote: > > > > > From: Roman Vivchar > > > > > > The mt6323 PMIC includes an AUXADC. Register the AUXADC in the mt6323 > > > devices array to allow the corresponding driver to probe using compatible > > > string. > > > > > > Tested-by: Ben Grisdale # Amazon Echo Dot (2nd Generation) > > > Signed-off-by: Roman Vivchar > > > --- > > > drivers/mfd/mt6397-core.c | 3 +++ > > > 1 file changed, 3 insertions(+) > > > > Doesn't apply. Please rebase and resent with my: > > > > Acked-by: Lee Jones > > There's a slight cross-tree conflict. Jonathan has already picked > patch 1 and patch 2 to the iio testing tree. This mfd patch doesn't > apply because recently merged mt6323 efuse patch (bde6556744888). > > The iio tree doesn't include mt6323 efuse patch, and there was some > dt-bindings merge conflict. > Should I rebase on top of linux-next and send mfd as a standalone patch? No cross-tree conflict. It doesn't apply because MFD has one of your earlier patches: bde655674488 ("mfd: mt6397-core: Add mt6323 EFUSE support") Rebase onto either Next or for-mfd-next. -- Lee Jones