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 D9B6F263C8F for ; Fri, 16 Jan 2026 13:22:42 +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=1768569762; cv=none; b=j1m//QrhOhWuls4kUlBXreL4afiiS1t5rdaLUjm/feYm+y+ACiUuLY5Eb9UiEGfCq0OgR+5bzA7vZgQ80/8r+h8XlLxir+vd7LpZcn6KjchDT05wzQi9M55Bq/vwM7XNUeOGx0Rn3/t36AqwRpwmZLe7jokEUlFHMj9vDYVHD0o= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768569762; c=relaxed/simple; bh=j4wHIgmvMJVXOW1N+YnRfkMMd2oTfCwWt7X6knBJR6Q=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date: MIME-Version:Content-Type; b=UidbQ8ofYEgduUU+AfJfdcjxj659HmFNzG6Vo2pVNM8PJYN4/1F2JD94r7YfA/3U/OU7qKh0dh38Wqvw5AIamejK+Lqbg7MKFGlP9DXj9/ACT5pJlH36gMpCvuLksv2lZ4xREuMjT/vhLXCkJZpdkGKMAAX6sIQgmY9QD+gIlgo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=dL/kuL+7; 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="dL/kuL+7" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 9BA17C116C6; Fri, 16 Jan 2026 13:22:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1768569762; bh=j4wHIgmvMJVXOW1N+YnRfkMMd2oTfCwWt7X6knBJR6Q=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=dL/kuL+7mBFlApUH9lxi9NRT+1tTkv6kFd1/6GtvkvC3/OUqsrE/YHnNTOEgaCBtu vzruiaGCVE4Oq4Nr/fzPNkyjK29lQaCbK/u8xrhdAXsUT8UVxTguFZ3N6fFWBEb7dE pFRYGdJuAMAw8i7H6qwxHyaVmlYyxnL3IaZFfQ9oQDfNzhyb7vde4aIF+vOceVZIuJ FHVyF+s7XFjHVw5JANQaXW0RR4TKcBZ3GSTzJhP2XrH7xoCG0xyMJZF2Yl5pgfhS3B OhuAok99AV1OUiZrh3XkHo9BT1T8HicCNe4FAOfl4J+VF3Jn9V5b8mf1YP4adzCd4K B9/fJ4BJVDPFg== From: Mark Brown To: Greg Kroah-Hartman , "Rafael J . Wysocki" , Danilo Krummrich , Geert Uytterhoeven Cc: linux-kernel@vger.kernel.org, Geert Uytterhoeven In-Reply-To: <47872f8f4cf613e9710963bf871c6ac7b2ce81e8.1768494166.git.geert+renesas@glider.be> References: <47872f8f4cf613e9710963bf871c6ac7b2ce81e8.1768494166.git.geert+renesas@glider.be> Subject: Re: [PATCH v2] regmap: Enable REGMAP when REGMAP_SLIMBUS is enabled Message-Id: <176856976035.65534.17705282773581631797.b4-ty@kernel.org> Date: Fri, 16 Jan 2026 13:22:40 +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: 7bit X-Mailer: b4 0.15-dev-47773 On Thu, 15 Jan 2026 17:24:02 +0100, Geert Uytterhoeven wrote: > Invisible symbol REGMAP defaults to y when any of the REGMAP_* symbols > is enabled, effectively auto-enabling it when needed. However, > REGMAP_SLIMBUS is missing from the list. > > Currently this does not cause any issues, as all symbols selecting > REGMAP_SLIMBUS also select REGMAP and/or REGMAP_IRQ. Add REGMAP_SLIMBUS > to the list for consistency, and to prevent any future issues. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next Thanks! [1/1] regmap: Enable REGMAP when REGMAP_SLIMBUS is enabled commit: dccc66b0e92d48d9a1908a3ccb8142e0ee3381f5 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