From: Michal Simek <michal.simek@amd.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v2 2/3] spi: xilinx: Add necessary inclusion and forward declaration
Date: Tue, 12 Mar 2024 15:18:53 +0100 [thread overview]
Message-ID: <56d4b666-23ea-4faf-8320-5006c0bcf937@amd.com> (raw)
In-Reply-To: <20240308162920.46816-3-andriy.shevchenko@linux.intel.com>
On 3/8/24 17:27, Andy Shevchenko wrote:
> xilinx_spi.h is mnissing inclusion and forward declaration, add them.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> include/linux/spi/xilinx_spi.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/include/linux/spi/xilinx_spi.h b/include/linux/spi/xilinx_spi.h
> index fd6add419e94..4ba8f53ce570 100644
> --- a/include/linux/spi/xilinx_spi.h
> +++ b/include/linux/spi/xilinx_spi.h
> @@ -2,6 +2,10 @@
> #ifndef __LINUX_SPI_XILINX_SPI_H
> #define __LINUX_SPI_XILINX_SPI_H
>
> +#include <linux/types.h>
> +
> +struct spi_board_info;
> +
> /**
> * struct xspi_platform_data - Platform data of the Xilinx SPI driver
> * @num_chipselect: Number of chip select by the IP.
Acked-by: Michal Simek <michal.simek@amd.com>
Thanks,
Michal
next prev parent reply other threads:[~2024-03-12 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 16:27 [PATCH v2 0/3] spi: xilinx: Massage xilinx_spi.h Andy Shevchenko
2024-03-08 16:27 ` [PATCH v2 1/3] spi: xilinx: Fix kernel documentation in the xilinx_spi.h Andy Shevchenko
2024-03-08 16:27 ` [PATCH v2 2/3] spi: xilinx: Add necessary inclusion and forward declaration Andy Shevchenko
2024-03-12 14:18 ` Michal Simek [this message]
2024-03-08 16:27 ` [PATCH v2 3/3] spi: xilinx: Make num_chipselect 8-bit in the struct xspi_platform_data Andy Shevchenko
2024-03-12 14:19 ` Michal Simek
2024-03-26 12:39 ` [PATCH v2 0/3] spi: xilinx: Massage xilinx_spi.h Mark Brown
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=56d4b666-23ea-4faf-8320-5006c0bcf937@amd.com \
--to=michal.simek@amd.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).