[PATCH] spi: tools: Add include folder to .gitignore

Francesco Lavra posted 1 patch 17 hours ago
tools/spi/.gitignore | 1 +
1 file changed, 1 insertion(+)
[PATCH] spi: tools: Add include folder to .gitignore
Posted by Francesco Lavra 17 hours ago
The Makefile for the SPI tools creates an include/linux/spi folder and some
symlinks inside it. After running `make -C spi/tools`, this folder shows up
as untracked in the git status.
Add the above folder to the .gitignore file.

Fixes: f325b73dc4db ("spi: tools: move to tools buildsystem")
Signed-off-by: Francesco Lavra <flavra@baylibre.com>
---
 tools/spi/.gitignore | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tools/spi/.gitignore b/tools/spi/.gitignore
index 14ddba3d2195..038261b34ed8 100644
--- a/tools/spi/.gitignore
+++ b/tools/spi/.gitignore
@@ -1,3 +1,4 @@
 # SPDX-License-Identifier: GPL-2.0-only
 spidev_fdx
 spidev_test
+include/
-- 
2.39.5
Re: [PATCH] spi: tools: Add include folder to .gitignore
Posted by Mark Brown 12 hours ago
On Mon, 09 Feb 2026 10:50:01 +0100, Francesco Lavra wrote:
> The Makefile for the SPI tools creates an include/linux/spi folder and some
> symlinks inside it. After running `make -C spi/tools`, this folder shows up
> as untracked in the git status.
> Add the above folder to the .gitignore file.
> 
> 

Applied to

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

Thanks!

[1/1] spi: tools: Add include folder to .gitignore
      commit: 5af56f30c4fcbade4a92f94dadfea517d1db9703

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