linux-kernel - Re: [PATCH v3] regmap: spi: Set regmap max raw r/w from max_transfer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <163501902912.919171.448046009962211592.b4-ty@kernel.org>
Date:   Sat, 23 Oct 2021 20:58:05 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        André Almeida <andrealmeid@...labora.com>,
        "Rafael J . Wysocki" <rafael@...nel.org>
Cc:     Mark Brown <broonie@...nel.org>, kernel@...labora.com,
        linux-kernel@...r.kernel.org,
        Lucas Tanure <tanureal@...nsource.cirrus.com>,
        Charles Keepax <ckeepax@...nsource.cirrus.com>
Subject: Re: [PATCH v3] regmap: spi: Set regmap max raw r/w from max_transfer_size

On Thu, 21 Oct 2021 10:27:21 -0300, André Almeida wrote:
> From: Lucas Tanure <tanureal@...nsource.cirrus.com>
> 
> Set regmap raw read/write from spi max_transfer_size
> so regmap_raw_read/write can split the access into chunks
> 
> 

Applied to

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

Thanks!

[1/1] regmap: spi: Set regmap max raw r/w from max_transfer_size
      commit: f231ff38b7b23197013b437128d196710fe282da

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