Received-SPF: pass (google.com: domain of linux-kernel+bounces-102249-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Wed, 13 Mar 2024 13:16:29 -0400
From: Sasha Levin <sashal@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Ansuel Smith <ansuelsmth@gmail.com>
Subject: Re: [PATCH 5.15 72/76] regmap: allow to define reg_update_bits for
 no bus configuration
Message-ID: <ZfHfbYg8HmIRsdBV@sashalap>
References: <20240313164223.615640-1-sashal@kernel.org>
 <20240313164223.615640-73-sashal@kernel.org>
 <6274f1ce-f2e0-414b-b9a9-bf2840fefd90@sirena.org.uk>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <6274f1ce-f2e0-414b-b9a9-bf2840fefd90@sirena.org.uk>

On Wed, Mar 13, 2024 at 04:46:04PM +0000, Mark Brown wrote:
>On Wed, Mar 13, 2024 at 12:42:19PM -0400, Sasha Levin wrote:
>> From: Ansuel Smith <ansuelsmth@gmail.com>
>>
>> [ Upstream commit 02d6fdecb9c38de19065f6bed8d5214556fd061d ]
>>
>> Some device requires a special handling for reg_update_bits and can't use
>> the normal regmap read write logic. An example is when locking is
>> handled by the device and rmw operations requires to do atomic operations.
>> Allow to declare a dedicated function in regmap_config for
>> reg_update_bits in no bus configuration.
>
>This is fairly clearly new functionality?

It is, but like the other commit, this new functionality is needed for a
later fix. We indicate this in the commit message by adding a trailer:

	Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
	Link: https://lore.kernel.org/r/20211104150040.1260-1-ansuelsmth@gmail.com
	Signed-off-by: Mark Brown <broonie@kernel.org>
	Stable-dep-of: 3f42b142ea11 ("serial: max310x: fix IO data corruption in batched operations")
	  ^^^^^^^^^
	Signed-off-by: Sasha Levin <sashal@kernel.org>

-- 
Thanks,
Sasha