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 123A6C00528 for ; Fri, 21 Jul 2023 08:54:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231496AbjGUIyR (ORCPT ); Fri, 21 Jul 2023 04:54:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54088 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231251AbjGUIyI (ORCPT ); Fri, 21 Jul 2023 04:54:08 -0400 Received: from madras.collabora.co.uk (madras.collabora.co.uk [46.235.227.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1B6E530EA; Fri, 21 Jul 2023 01:53:56 -0700 (PDT) Received: from [192.168.1.100] (2-237-20-237.ip236.fastwebnet.it [2.237.20.237]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: kholk11) by madras.collabora.co.uk (Postfix) with ESMTPSA id E2406660709B; Fri, 21 Jul 2023 09:53:53 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1689929634; bh=ffw2ebh9MH9Vj8Efzuv/Nuu595JTYxBbopA83mVf6zA=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=orGIBjYu+/go1gVsfDbth2LtGWUYY62TI6MVc6tGgJbFb2EvtgzoT4COfPU8kmCxT PZcQvDUjGyKaPSNmaetkwhh/txGhaHDPnRNnK8ON2/vfuoq8EkRAVeiRwWd+mDAYvw 9b1CiZn+r2L2AJVbhoyRrZ99USPYwSnyWldw8p/G24fldbKKSv69oCUkVW2QjkNCxG 8JtvsneNK6GsTluXVAXrHazPKlDMNP6Tq0ChzZb3kB8UzHMkgQN6DPfz4OMKAk32c3 3EajEW8Hxcg+t05oeazMWceeL6YaKmn36nqbJOOwTycYotnOWAb6d8zOMwTentrOS0 oKpLnfqgriJwA== Message-ID: Date: Fri, 21 Jul 2023 10:53:51 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: [PATCH RESEND v2 3/7] regulator: mt6358: Fix incorrect VCN33 sync error message Content-Language: en-US To: Chen-Yu Tsai , Lee Jones , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Mark Brown , Liam Girdwood , Matthias Brugger Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org, Fei Shao References: <20230721082903.2038975-1-wenst@chromium.org> <20230721082903.2038975-4-wenst@chromium.org> From: AngeloGioacchino Del Regno In-Reply-To: <20230721082903.2038975-4-wenst@chromium.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Il 21/07/23 10:28, Chen-Yu Tsai ha scritto: > After syncing the enable status of VCN33_WIFI to VCN33_BT, the driver > will disable VCN33_WIFI. If it fails it will error out with a message. > However the error message incorrectly refers to VCN33_BT. > > Fix the error message so that it correctly refers to VCN33_WIFI. > > Suggested-by: Fei Shao > Fixes: 65bae54e08c1 ("regulator: mt6358: Merge VCN33_* regulators") > Signed-off-by: Chen-Yu Tsai Reviewed-by: AngeloGioacchino Del Regno