From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7FC5E2ECE86 for ; Mon, 12 Jan 2026 14:31:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768228264; cv=none; b=TIXtjPiLEees+KQFpnaZ4BYBHOAML94lTKUTXCAGTONnbqbRSqzL/HomjfJKHR/XMwiCCTueAWcSt01phREzFuI963H+c2iCCysaU5S+67Cnd6U/pyBLeMwUyeUC6jtq+eMev/hD8P/dQZ8Emr3EoutoxKHXgQAo6SJCNZFeFx4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768228264; c=relaxed/simple; bh=l1RsPqz+gx8zYSw0pxuRzvNfjm5WoQTkPoCwdbC297I=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date: MIME-Version:Content-Type; b=AT16F32TNgLanvNAxBsHr7am9wQ+49TUGV1MvqEhHgAQ45iIOzNDcqaXlBLQnZsJO333epEWC12c5U0p0YpLNTK5LZUUDx6vPzERY0xRKMbMMionStbFDvM6W6GVhfPOTH8c7+/CBEXFXPd+3RY33Ip62R8N/gq4TcKT1eToGFE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Ite7pRv0; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Ite7pRv0" Received: by smtp.kernel.org (Postfix) with ESMTPSA id DF3A7C16AAE; Mon, 12 Jan 2026 14:31:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1768228264; bh=l1RsPqz+gx8zYSw0pxuRzvNfjm5WoQTkPoCwdbC297I=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=Ite7pRv0GAslm4Y8qKx0vs7ICGqtR9C/9pbKCarb0frefAvq1umAnUiJJvOxnGEXk NkmYZtlEY9qG4jpLlo6PB4uWEr+kCTRFXThEa0mSz3xATTDW5/Ih/4b6cXZpbwYpWk csYaXIvF+GR+8X9H85Rf8tfyJLRjXKV9RH2ICH1nW2p6AMqUiOjTQaLNFBW+j+zzPa w0J5A0hsY+NjNOk7YjCO1s6TMySKoDfnWWKPIUD/Z8e5pa/CRm8NBrM1v7XbXKXSHy LnbDt1Z0DuYz1QYACQgN8/I2ybA/HdPBaZObiJ07TxNBtOwAsidpU56rcgNtmvCWe8 TSekUUxwct8AQ== From: Mark Brown To: Liam Girdwood , Javier Martinez Canillas , Jon Hunter , Dmitry Baryshkov , Oleksij Rempel , =?utf-8?q?Andr=C3=A9_Draszik?= Cc: Peter Griffin , Tudor Ambarus , Will McVicker , Juan Yescas , kernel-team@android.com, linux-kernel@vger.kernel.org In-Reply-To: <20260109-regulators-defer-v2-0-1a25dc968e60@linaro.org> References: <20260109-regulators-defer-v2-0-1a25dc968e60@linaro.org> Subject: Re: [PATCH v2 0/8] regulator: core: allow regulator_register() with missing required supply Message-Id: <176822826163.92368.16808418574188317303.b4-ty@kernel.org> Date: Mon, 12 Jan 2026 14:31:01 +0000 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Mailer: b4 0.15-dev-47773 On Fri, 09 Jan 2026 08:38:36 +0000, André Draszik wrote: > With these attached patches it becomes possible again to support > hardware designs with multiple PMICs where individual rails of each act > as required supplies for rails of the other (due to the latter being > e.g. always-on), and vice-versa. > > Google Pixel 6 and 6 Pro (oriole and raven) are examples of such > designs. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/8] regulator: core: update two debug messages commit: 96e7a88d32de2554a5d7e54e87eb03d445dd6924 [2/8] regulator: core: fix locking in regulator_resolve_supply() error path commit: 497330b203d2c59c5ff3fa4c34d14494d7203bc3 [3/8] regulator: core: move supply check earlier in set_machine_constraints() commit: 86a8eeb0e913f4b6a55dabba5122098d4e805e55 [4/8] regulator: core: streamline supply resolution for always-on/boot-on regulators commit: 4f3323b752bfcc185c98ce4fb841cca8b700a7c0 [5/8] regulator: core: remove dead code in regulator_resolve_supply() commit: bdbdc4b398254597c9b6ac279f336750996bc0a6 [6/8] regulator: core: don't ignore errors from event forwarding setup commit: e23c0a59dabae9166bbea26fc05d08e7d9e900b7 [7/8] regulator: core: reresolve unresolved supplies when available commit: 304f5784e97281f18ef4bed574cbe5fcf6ce2f2e [8/8] regulator: core: don't fail regulator_register() with missing required supply commit: 8d38423d9dea7353a8a54a3ab2e0d0aa04ed34d0 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