Received-SPF: pass (google.com: domain of linux-kernel+bounces-17850-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>, 
 Naresh Solanki <naresh.solanki@9elements.com>
Cc: mazziesaccount@gmail.com, linux-kernel@vger.kernel.org
In-Reply-To: <20240104141314.3337037-1-naresh.solanki@9elements.com>
References: <20240104141314.3337037-1-naresh.solanki@9elements.com>
Subject: Re: [PATCH] regulator: event: Ensure atomicity for sequence number
Message-Id: <170445989773.6633.7562365006999842625.b4-ty@kernel.org>
Date: Fri, 05 Jan 2024 13:04:57 +0000
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Thu, 04 Jan 2024 19:43:13 +0530, Naresh Solanki wrote:
> Previously, the sequence number in the regulator event subsystem was
> updated without atomic operations, potentially leading to race
> conditions. This commit addresses the issue by making the sequence
> number atomic.
> 
> 

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: event: Ensure atomicity for sequence number
      commit: 1cadc04c1a1ac5015c2eb0fadfabf4b61bbe167e

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