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 196F2C43334 for ; Tue, 19 Jul 2022 18:48:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238528AbiGSSsm (ORCPT ); Tue, 19 Jul 2022 14:48:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43886 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237103AbiGSSsf (ORCPT ); Tue, 19 Jul 2022 14:48:35 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 89B51550E0 for ; Tue, 19 Jul 2022 11:48:34 -0700 (PDT) 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 1F48161799 for ; Tue, 19 Jul 2022 18:48:34 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 94896C341C6; Tue, 19 Jul 2022 18:48:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1658256513; bh=FPj+PzUSyU21yajg2aJqxdlA2Q5B3EZYxVIDft8PGgM=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=IjLSxpJOip1e/q0DBRT2GMNS+cv8hHPdoniROg3MJdLacs0sW5Sq56FLjrtvMcA/r 8MgsIQnmvuDVEb/5FxlV9J58/MoZV3mOAyALhMWLO4xw6gAN+4hGEE5Lhzv6CRQUvw vVURCTuMz6WeiLGZibUroLa4dMDDrv7c20takJ9JiuBrHgyhAE56VRM2w5JG9ACaVx ONKQPIg5wrH9vxXnsjTp/AHheUT6Qgs/cx4kEXFphEnCJc2ka0QnsqNvW6jWcyGeEl zpY6A/SnKhIbAgKK4SwYR349NDWHv78UUdrmce7O3oViUravQFKTHvhmJEzTx1CKGn vjvs2BK5RP1Dw== From: Mark Brown To: christian@kohlschutter.com Cc: linux-kernel@vger.kernel.org, lgirdwood@gmail.com In-Reply-To: References: <3270C618-E361-4BC1-B63A-917AE09DA60E@kohlschuetter.com> Subject: Re: [PATCH REBASE] regulator: core: Fix off-on-delay-us for always-on/boot-on regulators Message-Id: <165825651232.448796.18429380716580437688.b4-ty@kernel.org> Date: Tue, 19 Jul 2022 19:48:32 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 19 Jul 2022 16:02:00 +0200, Christian Kohlschütter wrote: > Regulators marked with "regulator-always-on" or "regulator-boot-on" > as well as an "off-on-delay-us", may run into cycling issues that are > hard to detect. > > This is caused by the "last_off" state not being initialized in this > case. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/1] regulator: core: Fix off-on-delay-us for always-on/boot-on regulators commit: 218320fec29430438016f88dd4fbebfa1b95ad8d 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