[PATCH v2] spi: bitbang: Drop duplicated word in file header comment

[PATCH v2] spi: bitbang: Drop duplicated word in file header comment

[Saad Anjum]

Commit 8ee46db14169 ("spi: bitbang: Add missing MODULE_DESCRIPTION()")
updated the terminology in the file header from "SPI master controller"
to "SPI host controller", but only the word "master" was replaced, so the
header now says "controller" twice in a row.

Drop the duplicated "controller" so that the comment matches the wording
used by the Kconfig entry and the MODULE_DESCRIPTION() string.

No functional change.

Signed-off-by: Saad Anjum <saadanjum239@gmail.com>
---
v2: Resending with the correct From/Signed-off-by - v1 went out under the
wrong identity by mistake, sorry for the noise.

 drivers/spi/spi-bitbang.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/spi/spi-bitbang.c b/drivers/spi/spi-bitbang.c
index fb288ed56..347265e80 100644
--- a/drivers/spi/spi-bitbang.c
+++ b/drivers/spi/spi-bitbang.c
@@ -1,6 +1,6 @@
 // SPDX-License-Identifier: GPL-2.0-or-later
 /*
- * Polling/bitbanging SPI host controller controller driver utilities
+ * Polling/bitbanging SPI host controller driver utilities
  */
 
 #include <linux/spinlock.h>

base-commit: ce1e0223d8ad4211275c82a17ed6d43ab81e13d9
-- 
2.50.1 (Apple Git-155)

Re: [PATCH v2] spi: bitbang: Drop duplicated word in file header comment

[Mark Brown]

On Fri, 02 Oct 2026 20:55:27 +0500, Saad Anjum wrote:
> spi: bitbang: Drop duplicated word in file header comment

Applied to

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

Thanks!

[1/1] spi: bitbang: Drop duplicated word in file header comment
      https://git.kernel.org/broonie/spi/c/65766f75dce3

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