Received-SPF: pass (google.com: domain of linux-kernel+bounces-204718-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: Mark Brown <broonie@kernel.org>
To: linux-kernel@vger.kernel.org, 
 Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, 
 "Rafael J. Wysocki" <rafael@kernel.org>
In-Reply-To: <20240605205315.19132-1-andy.shevchenko@gmail.com>
References: <20240605205315.19132-1-andy.shevchenko@gmail.com>
Subject: Re: [PATCH v1 1/1] regmap: spi: Fix potential off-by-one when
 calculating reserved size
Message-Id: <171769221292.1599563.14121347074593824634.b4-ty@kernel.org>
Date: Thu, 06 Jun 2024 17:43:32 +0100
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Wed, 05 Jun 2024 23:53:15 +0300, Andy Shevchenko wrote:
> If we ever meet a hardware that uses weird register bits and padding,
> we may end up in off-by-one error since x/8 + y/8 might not be equal
> to (x + y)/8 in some cases.
> 
> bits    pad   x/8+y/8 (x+y)/8
> 4..7    0..3    0       0 // x + y from 4 up to 7
> 4..7    4..7    0       1 // x + y from 8 up to 11
> 4..7    8..11   1       1 // x + y from 12 up to 15
> 8..15   0..7    1       1 // x + y from 8 up to 15
> 8..15   8..15   2       2 // x + y from 16 up to 23
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: spi: Fix potential off-by-one when calculating reserved size
      commit: d4ea1d504d2701ba04412f98dc00d45a104c52ab

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