mbox series

[00/11] spi: Fix ERRORs reported by checkpatch

Message ID 1616566602-13894-1-git-send-email-f.fangjian@huawei.com (mailing list archive)
Headers show
Series spi: Fix ERRORs reported by checkpatch | expand

Message

Jay Fang March 24, 2021, 6:16 a.m. UTC
Hi,

A total of 27 ERRORs are found when scanning all files in the drivers/spi
directory by checkpatch tool. This series fixes 21 ERRORs of them, and the
remaining 6 ERRORs I don't think need to be fixed.

No functional change.


Thanks,
Jay

Jay Fang (11):
  spi: spi-topcliff-pch: Fix checkpatch spacing error
  spi: sprd: Fix checkpatch spacing error
  spi: pxa2xx: Fix checkpatch spacing errors
  spi: omap-100k: Fix checkpatch spacing errors
  spi: spi-mtk-nor: Fix checkpatch spacing error
  spi: dln2: Fix open brace following function definitions go on the
    next line
  spi: spi-bitbang: Fix open brace following function definitions go on
    the next line
  spi: jcore: Fix trailing statements should be on next line
  spi: spi-mem: Fix code indent should use tabs where possible
  spi: rockchip: Fix code indent should use tabs where possible
  spi: pl022: Fix trailing whitespace

 drivers/spi/spi-bitbang.c      | 9 ++++++---
 drivers/spi/spi-dln2.c         | 3 ++-
 drivers/spi/spi-jcore.c        | 3 ++-
 drivers/spi/spi-mem.c          | 6 +++---
 drivers/spi/spi-mtk-nor.c      | 2 +-
 drivers/spi/spi-omap-100k.c    | 8 ++++----
 drivers/spi/spi-pl022.c        | 2 +-
 drivers/spi/spi-pxa2xx-pci.c   | 2 +-
 drivers/spi/spi-pxa2xx.c       | 2 +-
 drivers/spi/spi-rockchip.c     | 6 +++---
 drivers/spi/spi-sprd-adi.c     | 2 +-
 drivers/spi/spi-topcliff-pch.c | 3 ++-
 12 files changed, 27 insertions(+), 21 deletions(-)

Comments

Mark Brown March 24, 2021, 11:39 p.m. UTC | #1
On Wed, 24 Mar 2021 14:16:31 +0800, Jay Fang wrote:
> A total of 27 ERRORs are found when scanning all files in the drivers/spi
> directory by checkpatch tool. This series fixes 21 ERRORs of them, and the
> remaining 6 ERRORs I don't think need to be fixed.
> 
> No functional change.
> 
> 
> [...]

Applied to

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

Thanks!

[01/11] spi: spi-topcliff-pch: Fix checkpatch spacing error
        commit: c9831087356b7ae02dfb22b3121117c48aa9e95b
[02/11] spi: sprd: Fix checkpatch spacing error
        commit: e13a870ffaa60f459892eb4600a286b4db7da5ad
[03/11] spi: pxa2xx: Fix checkpatch spacing errors
        commit: c07caca3cea90332e410ba3e53bc264ae1f2c9c9
[04/11] spi: omap-100k: Fix checkpatch spacing errors
        commit: f2edb98e806d0bf7947e5da352d69f4fbb063b04
[05/11] spi: spi-mtk-nor: Fix checkpatch spacing error
        commit: 99b3a36204564cb689cd862794043e1b8f5863b1
[06/11] spi: dln2: Fix open brace following function definitions go on the next line
        commit: 211f8a0a39cd7dcd9c14744053ea681a0e7eb36d
[07/11] spi: spi-bitbang: Fix open brace following function definitions go on the next line
        commit: f96c19fab393db16a2db78183ca8f584ee1b716a
[08/11] spi: jcore: Fix trailing statements should be on next line
        commit: 45793de7bf89fbd0fd1e2db9dda4e58a9c1395ee
[09/11] spi: spi-mem: Fix code indent should use tabs where possible
        commit: 6ca6ad908e965b1b01c31618971a1de7b6307a21
[10/11] spi: rockchip: Fix code indent should use tabs where possible
        commit: 02621799966babf50d1d1dc523e834366904b55d
[11/11] spi: pl022: Fix trailing whitespace
        commit: 9d5376872162dc70c16ae8379dba0266f35883f9

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