linux-kernel - Re: [PATCH] spi: tools: make a symbolic link to the header file spi.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 22 Apr 2021 17:48:44 +0100
From:   Mark Brown <broonie@...nel.org>
To:     quanyang.wang@...driver.com,
        Alexandru Ardelean <alexandru.ardelean@...log.com>,
        Andy Shevchenko <andy.shevchenko@...il.com>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        linux-spi@...r.kernel.org
Subject: Re: [PATCH] spi: tools: make a symbolic link to the header file spi.h

On Thu, 22 Apr 2021 18:26:04 +0800, quanyang.wang@...driver.com wrote:
> 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.

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