Received-SPF: pass (google.com: domain of linux-kernel+bounces-206677-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>, 
 linux-kernel@vger.kernel.org, 
 Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, 
 "Rafael J. Wysocki" <rafael@kernel.org>
In-Reply-To: <20240606202102.3108729-1-andriy.shevchenko@linux.intel.com>
References: <20240606202102.3108729-1-andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v1 1/1] regmap: kunit: Use array_size() and
 sizeof(*ptr) consistently
Message-Id: <171778963013.87562.14562841189265685482.b4-ty@kernel.org>
Date: Fri, 07 Jun 2024 20:47:10 +0100
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Thu, 06 Jun 2024 23:21:02 +0300, Andy Shevchenko wrote:
> Some of the allocations use explit sizeof(type) instead of sizeof(*ptr),
> which is fragile. In particular, stress_insert() allocates double
> of memory without obvious need for a test. Convert all allocations
> to use array_size() and sizeof(*ptr) to eliminate similar mistakes
> or wrong memory sizes.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: kunit: Use array_size() and sizeof(*ptr) consistently
      commit: f82ecf76cdd477c64b09f328aaa182c1dc64dd8b

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