Re: [PATCH v3 0/7] spi: dw: Cleanup macros/funcs naming and add IP-core version support
From: Mark Brown
Date: Tue Nov 16 2021 - 12:48:50 EST
On Mon, 15 Nov 2021 21:19:10 +0300, Serge Semin wrote:
> I was going to submit a cleanup patchset for the DW SSI driver for a
> long time, but due to lack of free time couldn't make it so far.
> Nandhini's series [1] made me to proceed with this task so mate would
> finally have his patchset accepted and merged into the mainline kernel.
>
> There are four cleanup patches here and three feature patches. In the
> framework of the former patches we convert the DW SPI driver to using
> module namespaces and provide a better code organization. In particular
> the second part concerns the methods and macros naming unification (using
> a unified prefixes of the code object names) and the CSR fields macro
> implementation using the bitfield helpers available in the kernel. The
> later patches introduce the DW SSI IP-core versions interface so it
> could be used for a version-specific features implementation. Nandhini
> will be mostly interested in the later patches in the framework of his
> series [1].
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/7] spi: dw: Add a symbols namespace for the core module
commit: a62bacba81c477a6fd8f15da593ad02305a3d6da
[2/7] spi: dw: Discard redundant DW SSI Frame Formats enumeration
commit: 21b6b3809b840ad3d3f0689aac227929c04e9518
[3/7] spi: dw: Put the driver entities naming in order
commit: 725b0e3ea899ff1cb799756ade302e7bc13a8559
[4/7] spi: dw: Convert to using the Bitfield access macros
commit: ec77c086dc5b2eb422ff588f91cc011137fa9ea3
[5/7] spi: dw: Introduce Synopsys IP-core versions interface
commit: 2cc8d9227bbba7d6f3790a86f1ff0d665a75f3b8
[6/7] spi: dw: Replace DWC_HSSI capability with IP-core version checker
commit: 2b8a47e0b6984b9795baa20ddcbd37e9ea9b2a91
[7/7] spi: dw: Define the capabilities in a continuous bit-flags set
commit: 44ebcb44584f81d1d38fafb45cf57d651f44616e
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