One minor correction to a comment and updating the allowed register
sizes for the SoundWire register map, to allow support of additional
hardware.

NOTE: The second patch requires the patch commit 62dc9f3f2fd0
("soundwire: bus: export sdw_nwrite_no_pm and sdw_nread_no_pm
functions") from Vinod's SoundWire tree to build, so not sure if we want
to push these patches through his tree or merge his tree across.

Thanks,
Charles

Charles Keepax (1):
  regmap: sdw: Update misleading comment

Lucas Tanure (1):
  regmap: sdw: Remove 8-bit value size restriction

 drivers/base/regmap/regmap-sdw.c | 41 +++++++++++++++++++-------------
 1 file changed, 25 insertions(+), 16 deletions(-)

-- 
2.30.2

On Thu, 12 Jan 2023 17:18:38 +0000, Charles Keepax wrote:
> One minor correction to a comment and updating the allowed register
> sizes for the SoundWire register map, to allow support of additional
> hardware.
> 
> NOTE: The second patch requires the patch commit 62dc9f3f2fd0
> ("soundwire: bus: export sdw_nwrite_no_pm and sdw_nread_no_pm
> functions") from Vinod's SoundWire tree to build, so not sure if we want
> to push these patches through his tree or merge his tree across.
> 
> [...]

Applied to

   broonie/regmap.git for-next

Thanks!

[1/2] regmap: sdw: Update misleading comment
      commit: 6466b376e927d51ea3eadc1965714305d8c3c066
[2/2] regmap: sdw: Remove 8-bit value size restriction
      commit: 522272047dc631610dd180be0c3670043bcdf42e

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