linux-kernel - Re: [PATCH v2] spi: intel: Update help text of PCI and Platform drivers

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: <167605578764.957618.11554851569704837842.b4-ty@kernel.org>
Date:   Fri, 10 Feb 2023 19:03:07 +0000
From:   Mark Brown <broonie@...nel.org>
To:     mika.westerberg@...ux.intel.com,
        Mauro Lima <mauro.lima@...ypsium.com>
Cc:     michael@...le.cc, linux-spi@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] spi: intel: Update help text of PCI and Platform
 drivers

On Fri, 10 Feb 2023 13:41:58 -0300, Mauro Lima wrote:
> Modern intel hardware uses controllers that work in hardware
> sequencing mode. In this mode, the controller exposes a subset
> of operations, like read, write and erase, making it easier
> and less error-prone for use.
> On the other hand, most of the controllers handled by the
> platform driver use software sequencing that exposes the
> entire set of operations i.e. exposes the low level SPI-NOR
> opcodes to the software for use.
> Update PCI and Platform help text with this information.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: intel: Update help text of PCI and Platform drivers
      commit: 2ea9b08a661274b9b7b182327bf6ffe29605d671

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