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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 04632EA4FC6 for ; Mon, 23 Feb 2026 14:46:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:MIME-Version:Date:Message-Id:Subject:References:In-Reply-To:Cc: To:From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=8dsGNhs/X2W16wd1pyLsNwJnTK0xSFKOeI3nGX+ZGPM=; b=xpu4EzWyuefTnQoAcRmtxLxEDg 36oZc/mEKfw1g9rukKkfrWXXhPEC3RKawgE/dCWBAA0Bz0BgCh6omDfFQMScPZ/LmHSX2AeozisbF A4Kedvp4tCWaYCZYx9B4q26+GEEo/q4stVPfg0QKmsso+U4DVCWikzSuJ7z72jMYz/+nLdZgN3/VD TOA/oF1Fo/N9tgI2GUhg4a4ZbWg9N3odoqIQG1uwsHnNioCvuhlf03l1LLiyyhtlLDoEhyNzRDZFf EDxonjiF+bWgiE43PhmdPG5wFFuZ5729HE+YOtBa6Xtb1Ot06hoRSkyVoaqJyhBScl1zyMbsEam4E VSn/iwzg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1vuXCW-00000000UpO-2Ps7; Mon, 23 Feb 2026 14:46:20 +0000 Received: from sea.source.kernel.org ([2600:3c0a:e001:78e:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1vuXCT-00000000Up1-1Tkb; Mon, 23 Feb 2026 14:46:18 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sea.source.kernel.org (Postfix) with ESMTP id A06B5407C9; Mon, 23 Feb 2026 14:46:15 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 52568C116C6; Mon, 23 Feb 2026 14:46:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1771857975; bh=teNVBJErbdtcUWBxBqB1OQagnnRI/zPyGSOOwMdkUNY=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=me/OJi+zmeH2vkjG9b4f82FAl9EM1UZzt69iajB21pITCljyf6YEPK2ufDGBErn4p GR3d5GxDZgTOn5eKSUrJfw8oZm3p3FEIdIW/ZL93xuaWEc+H1ZasIO1WFzEOiViaQI YKzQMNCr/6XWrALZ6/nIH7ZT2eDLpMs38KVXnSsgO3SIUihqNm9dYr/JUiXogqWCqz SpetGQ0CYqs9mnyEtmQ8FKCHW1kfoWksIWv36oiEjtoQ4o1AN6pEoeTltDd7C8yixO AJudpKBdPHE1ZIlmo5pUANfHzHi0370aqsAnoadrKeByTumiYPq//B5x/XxEtz0dEV Cy8rYDgAEu6Uw== From: Mark Brown To: Rob Herring , Krzysztof Kozlowski , Conor Dooley , Matthias Brugger , AngeloGioacchino Del Regno , Liam Girdwood , Hsin-Hsiung Wang , David Lechner Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org In-Reply-To: <20260219-mtk-mt6359-fix-regulator-names-v1-0-ee0fcebfe1d9@baylibre.com> References: <20260219-mtk-mt6359-fix-regulator-names-v1-0-ee0fcebfe1d9@baylibre.com> Subject: Re: (subset) [PATCH 0/2] arm64: dts: mediatek: mt6359: give regulators unique names Message-Id: <177185797303.229167.4225970079951259515.b4-ty@kernel.org> Date: Mon, 23 Feb 2026 14:46:13 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.15-dev-47773 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260223_064617_447432_EE9379BE X-CRM114-Status: GOOD ( 13.00 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, 19 Feb 2026 16:55:28 -0600, David Lechner wrote: > While working on this regulator in U-Boot, I noticed that the regulator > names were not unique. This is considered an error in U-Boot and we get > the following error messages: > > mt6359_regulator ldo_vrfck_1: 'regulator-name' has nonunique value: 'vrfck > mt6359_regulator ldo_vemc_1: 'regulator-name' has nonunique value: 'vemc > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [2/2] dt-bindings: regulator: mt6359: make regulator names unique commit: be704107e79696e855aa41e901a926039b6d2410 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