linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jay Fang <f.fangjian@huawei.com>
Cc: Mark Brown <broonie@kernel.org>,
	huangdaode@huawei.com, linux-spi@vger.kernel.org
Subject: Re: [PATCH 00/11] spi: Fix ERRORs reported by checkpatch
Date: Wed, 24 Mar 2021 23:39:33 +0000	[thread overview]
Message-ID: <161662883642.51717.4021125408436429442.b4-ty@kernel.org> (raw)
In-Reply-To: <1616566602-13894-1-git-send-email-f.fangjian@huawei.com>

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

      parent reply	other threads:[~2021-03-24 23:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24  6:16 [PATCH 00/11] spi: Fix ERRORs reported by checkpatch Jay Fang
2021-03-24  6:16 ` [PATCH 01/11] spi: spi-topcliff-pch: Fix checkpatch spacing error Jay Fang
2021-03-24  6:16 ` [PATCH 02/11] spi: sprd: " Jay Fang
2021-03-24  6:16 ` [PATCH 03/11] spi: pxa2xx: Fix checkpatch spacing errors Jay Fang
2021-03-24  6:16 ` [PATCH 04/11] spi: omap-100k: " Jay Fang
2021-03-24  6:16 ` [PATCH 05/11] spi: spi-mtk-nor: Fix checkpatch spacing error Jay Fang
2021-03-24  6:16 ` [PATCH 06/11] spi: dln2: Fix open brace following function definitions go on the next line Jay Fang
2021-03-24  6:16 ` [PATCH 07/11] spi: spi-bitbang: " Jay Fang
2021-03-24  6:16 ` [PATCH 08/11] spi: jcore: Fix trailing statements should be on " Jay Fang
2021-03-24  6:16 ` [PATCH 09/11] spi: spi-mem: Fix code indent should use tabs where possible Jay Fang
2021-03-24  6:16 ` [PATCH 10/11] spi: rockchip: " Jay Fang
2021-03-24  6:16 ` [PATCH 11/11] spi: pl022: Fix trailing whitespace Jay Fang
2021-03-24 23:39 ` Mark Brown [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=161662883642.51717.4021125408436429442.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=f.fangjian@huawei.com \
    --cc=huangdaode@huawei.com \
    --cc=linux-spi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).