Message ID | 20240207120431.2766269-1-tudor.ambarus@linaro.org |
---|---|
Headers | show |
Series | spi: s3c64xx: straightforward cleanup | expand |
On Wed, 07 Feb 2024 12:04:14 +0000, Tudor Ambarus wrote: > The patch set has no dependency although Sam prefers to have this simple > cleanup queued after the gs101 patches from: > https://lore.kernel.org/linux-spi/20240207111516.2563218-1-tudor.ambarus@linaro.org/ > > Tested with gs101-spi. > > Changes in v5: > - don't abuse the Fixes tag, it was wrongly used for: > - explicit header inclusions > - possible negative array index fix, which is just a posibility, > it never happened > - typo fix > - reorder patches, sort headers then explicitly include the missing ones > - new patch: "spi: s3c64xx: explicitly include <linux/types.h>" > - collect R-b tags > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [01/17] spi: s3c64xx: sort headers alphabetically commit: a77ce80f63f06d7ae933c332ed77c79136fa69b0 [02/17] spi: s3c64xx: explicitly include <linux/io.h> commit: 42a9ac378d918176e17592cbe79d8b0606f951e4 [03/17] spi: s3c64xx: explicitly include <linux/bits.h> commit: 4568fa574fcef3811a8140702979f076ef0f5bc0 [04/17] spi: s3c64xx: explicitly include <linux/types.h> commit: 7256d6bdd4fe0eac6d4bcd138c3d87f95f79c750 [05/17] spi: s3c64xx: avoid possible negative array index commit: a336d41bbea51e11e3e4f56bd3877a535c077129 [06/17] spi: s3c64xx: fix typo, s/configuartion/configuration commit: 97b63f4707046b2ef99d077dd4d333c3acca06ae [07/17] spi: s3c64xx: remove unneeded (void *) casts in of_match_table commit: 271f18816b3ba2f75785660e427c16585b7302f2 [08/17] spi: s3c64xx: remove else after return commit: 9d47e411f4d636519a8d26587928d34cf52c0c1f [09/17] spi: s3c64xx: move common code outside if else commit: 5d7f4f4367079992c7a1bb1654ffea87ddc82be8 [10/17] spi: s3c64xx: check return code of dmaengine_slave_config() commit: e9c49effde70fb4b10d0ad9c94b69fe6314fc608 [11/17] spi: s3c64xx: propagate the dma_submit_error() error code commit: 60dc8d342e933097eb82db5859edcac9077a6db5 [12/17] spi: s3c64xx: rename prepare_dma() to s3c64xx_prepare_dma() commit: 4c6452050530b741daf108de0c02cd2299f8f5d1 [13/17] spi: s3c64xx: return ETIMEDOUT for wait_for_completion_timeout() commit: 1a234accc93191a3a73eb4cc264abb6d79d63430 [14/17] spi: s3c64xx: drop blank line between declarations commit: 91a9b8e6b63eeb3634e736a4b65ae536c08155b2 [15/17] spi: s3c64xx: downgrade dev_warn to dev_dbg for optional dt props commit: f186d34071fb2a7db7249b09d5e1796b18b37d7d [16/17] spi: s3c64xx: remove duplicated definition commit: eb8096c30ad07e6201830816e398b3ad603cc096 [17/17] spi: s3c64xx: drop a superfluous bitwise NOT operation commit: acd6c7b1d2765fd30b7d7487aff50dc824db314e 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