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 3251BC05027 for ; Fri, 27 Jan 2023 00:54:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232828AbjA0AyC (ORCPT ); Thu, 26 Jan 2023 19:54:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42948 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232292AbjA0Ax7 (ORCPT ); Thu, 26 Jan 2023 19:53:59 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2D192530FD for ; Thu, 26 Jan 2023 16:53:56 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id BE860619CB for ; Fri, 27 Jan 2023 00:53:55 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 41F21C433EF; Fri, 27 Jan 2023 00:53:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1674780835; bh=PJHJ9/eLbz4lLsG9p3KtlaXfM4oLzuXTDQ8E2Hls+w8=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=ku1yF1KipVryMWdDMfHUHZ6XmekunQOyz5KbpG5RmZCAoqO+fgJooEI6S1mjDNODB Avzrmp9OCZcOb0VzmrJxj+JFqorGt9x6S43a2PrQ1igAxWvWat5ynK+sArUlQcsiYV IjsEVPjMzaJYBXSREcHWduxNM76MUpTpaP50ejmOTLRzkyZqGDozzOdf42lGaS4tzv CP15YMF1bfotCjvwTV1ofCKt0iLpKS96kcUBTcwvOnI16nezwJt7CjWlVNfpGS76yo xRW0jsemaUmnaRPM/CkGElZsA9pg317RQYbXN72RH+Eya8XUjbhjooB0jFpTeILGwP SaGOc/5LkvL1g== From: Mark Brown To: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Cristian Marussi Cc: sudeep.holla@arm.com, Jim Quinlan , Florian Fainelli In-Reply-To: <20230126180511.766373-1-cristian.marussi@arm.com> References: <20230126180511.766373-1-cristian.marussi@arm.com> Subject: Re: [PATCH] regulator: scmi: Allow for zero voltage domains Message-Id: <167478083297.1118403.15307034817786674476.b4-ty@kernel.org> Date: Fri, 27 Jan 2023 00:53:52 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.12.0 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 26 Jan 2023 18:05:11 +0000, Cristian Marussi wrote: > SCMI Voltage protocol allows the platform to report no voltage domains > on discovery, while warning the user about such an odd configuration. > As a consequence this condition should not be treated as error by the SCMI > regulator driver either. > > Allow SCMI regulator driver to probe successfully even when no voltage > domains are discovered. > > [...] Applied to broonie/regulator.git for-next Thanks! [1/1] regulator: scmi: Allow for zero voltage domains commit: 668f777d02f61faa834f1e24f3b99576dbe5ff6b All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark