spi: tools: make a symbolic link to the header file spi.h
PATCH 1/1 spi: tools: make a symbolic link to the header file spi.h
From: Quanyang Wang <[email protected]>
The header file spi.h in include/uapi/linux/spi is needed for spidev.h, so we also need make a symbolic link to it to eliminate the error message as below:
In file included from spidev_test.c:24:include/linux/spi/spidev.h:28:10: fatal error: linux/spi/spi.h: No such file or directory
28 | #include <linux/spi/spi.h>
| ^~~~~~~~~~~~~~~~~
compilation terminated.
--- tools/spi/Makefile | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
tools/spi/Makefile +3 -2
@@ -25,11 +25,12 @@ include $(srctree)/tools/build/Makefile.include # # We need the following to be outside of kernel tree # -$(OUTPUT)include/linux/spi/spidev.h: ../../include/uapi/linux/spi/spidev.h +$(OUTPUT)include/linux/spi: ../../include/uapi/linux/spi mkdir -p $(OUTPUT)include/linux/spi 2>&1 || true ln -sf $(CURDIR)/../../include/uapi/linux/spi/spidev.h $@ + ln -sf $(CURDIR)/../../include/uapi/linux/spi/spi.h $@ -prepare: $(OUTPUT)include/linux/spi/spidev.h +prepare: $(OUTPUT)include/linux/spi # # spidev_test
Signature · 1 line
2.25.1
Mark Brown
maintainerQuoted 9 lines · On Thu, 22 Apr 2021 18:26:04 +0800, [email protected] wrote:
The header file
spi.hininclude/uapi/linux/spiis needed forspidev.h, so we also need make a symbolic link to it to eliminate the error message as below:In file included from spidev_test.c:24:
include/linux/spi/spidev.h:28:10: fatal error:linux/spi/spi.h: No such file or directory
28 | #include <linux/spi/spi.h>| ^~~~~~~~~~~~~~~~~compilation terminated.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: tools: make a symbolic link to the header file spi.h
commit: bc2e9578baed90f36abe6bb922b9598a327b0555
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