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 42C7DC7EE2E for ; Tue, 23 May 2023 21:44:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238670AbjEWVo2 (ORCPT ); Tue, 23 May 2023 17:44:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38174 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238643AbjEWVoV (ORCPT ); Tue, 23 May 2023 17:44:21 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A3490FA; Tue, 23 May 2023 14:44:17 -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 125936368D; Tue, 23 May 2023 21:44:17 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8EF41C433EF; Tue, 23 May 2023 21:44:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1684878256; bh=Pcy27QxV2VSyKZ0c9gBpRqx5QQlOlbBSFETWOV2+EdI=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=ohrWebOdofNkYKggD8+jvJ3xc7Yb5SROIdSTiZbdW1jiRh+RKMNsakq11Fa5VAQqx zsfTW3+wtLfKBmArxSLLjet7u/dP1Hxuf3DVrNU4AJUSXS3keDPZIYo5gAKAV6+e0Y CtPzsbo4pMQxIGQX2TW4esVgn2i6xWrDHBP+4cQlSGXb24n5LD5SDFK5AEZaQ/5iwV 4+IZWvHaTee0QzKnAKp5j1U7D0fqicGThMKXGV1e3Ml367FxM9EnMPYEoAUS8fO82f nfkj/lkTPsQT+zKGSpSn6R/q97fGP51kucSwu3WRye3Ob4h4W56c0av6pQMmhFZdb9 runop5qF1Euag== From: Mark Brown To: Heiko Stuebner , Rob Herring , Krzysztof Kozlowski , Lee Jones , Sebastian Reichel Cc: Michael Turquette , Stephen Boyd , Linus Walleij , Liam Girdwood , Alexandre Belloni , Alessandro Zummo , linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, kernel@collabora.com In-Reply-To: <20230504173618.142075-1-sebastian.reichel@collabora.com> References: <20230504173618.142075-1-sebastian.reichel@collabora.com> Subject: Re: (subset) [PATCH v8 00/14] mfd/pinctrl/regulator: Add RK806 Support Message-Id: <168487825330.297228.86399112771503926.b4-ty@kernel.org> Date: Tue, 23 May 2023 22:44:13 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.13-dev-bfdf5 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 04 May 2023 19:36:04 +0200, Sebastian Reichel wrote: > All existing boards using RK3588/RK3588s use RK806 PMICs. This series is now > the main blocker for full upstream support of those boards and it would be good > to have it merged for 6.5 :) The patches have been tested on multiple different > platforms and are mainly missing an Ack from Mark or Liam for the rk808-regulator > changes. > > Merging must happen through a single tree, since the pinctrl and regulator > drivers rely on the register definitions from the include file added by the MFD > patch. My suggested merge strategy is that Lee creates an immutable branch for > the regulator/pinctrl tree once all Acks have been collected. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [10/14] regulator: expose regulator_find_closest_bigger commit: 431cb97b763133fba8b1c68c1ed089315f25e4dd [11/14] regulator: rk808: fix asynchronous probing commit: 1b9e86d445a0f5c6d8dcbaf11508cb5dfb5848a8 [12/14] regulator: rk808: cleanup parent device usage commit: 5111c931f36cebe77d4ce66964c348e6eb4afca0 [13/14] regulator: rk808: revert to synchronous probing commit: 22a94021e7d2b456c6abb59ad0a7ce4e94933d4a [14/14] regulator: rk808: add rk806 support commit: f991a220a44726c54c2332569a2a80bf074aa775 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