linux-kernel - Re: [PATCH v3] spi: amd: Configure device speed

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <166144584356.547508.3222609511396921392.b4-ty@kernel.org>
Date:   Thu, 25 Aug 2022 17:44:03 +0100
From:   Mark Brown <broonie@...nel.org>
To:     shreeya.patel@...labora.com, sanju.mehta@....com
Cc:     tanureal@...nsource.cirrus.com, alvaro.soliverez@...labora.com,
        krisman@...labora.com, linux-kernel@...r.kernel.org,
        kernel@...labora.com, linux-spi@...r.kernel.org
Subject: Re: [PATCH v3] spi: amd: Configure device speed

On Thu, 25 Aug 2022 20:01:32 +0530, Shreeya Patel wrote:
> From: Lucas Tanure <tanureal@...nsource.cirrus.com>
> 
> Number of clock frequencies are supported by AMD controller
> which are mentioned in the amd_spi_freq structure table.
> 
> Create mechanism to configure device clock frequency such
> that it is strictly less than the requested frequency.
> 
> [...]

Applied to

   broonie/spi.git for-next

Thanks!

[1/1] spi: amd: Configure device speed
      commit: 3fe26121dc3a9bf64e18fe0075cd9a92c9cd1b1a

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