From: Andi Shyti <andi@etezian.org>
To: Jaewon Kim <jaewon02.kim@samsung.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andi Shyti <andi@etezian.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
linux-spi@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: s3c64xx: add no_cs description
Date: Mon, 6 Mar 2023 10:06:56 +0100 [thread overview]
Message-ID: <ZAWtMIDHGd+nBTA1@intel.intel> (raw)
In-Reply-To: <20230306014239.80570-1-jaewon02.kim@samsung.com>
Hi Jaewon,
On Mon, Mar 06, 2023 at 10:42:39AM +0900, Jaewon Kim wrote:
> This patch adds missing variable no_cs descriptions.
>
> Signed-off-by: Jaewon Kim <jaewon02.kim@samsung.com>
Reviewed-by: Andi Shyti <andi@etezian.org>
Thanks,
Andi
> ---
> include/linux/platform_data/spi-s3c64xx.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/platform_data/spi-s3c64xx.h b/include/linux/platform_data/spi-s3c64xx.h
> index 5df1ace6d2c9..3101152ce449 100644
> --- a/include/linux/platform_data/spi-s3c64xx.h
> +++ b/include/linux/platform_data/spi-s3c64xx.h
> @@ -29,6 +29,7 @@ struct s3c64xx_spi_csinfo {
> * struct s3c64xx_spi_info - SPI Controller defining structure
> * @src_clk_nr: Clock source index for the CLK_CFG[SPI_CLKSEL] field.
> * @num_cs: Number of CS this controller emulates.
> + * @no_cs: Used when CS line is not connected.
> * @cfg_gpio: Configure pins for this SPI controller.
> */
> struct s3c64xx_spi_info {
> --
> 2.17.1
next prev parent reply other threads:[~2023-03-06 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230306015413epcas2p371356e4008af6978cdadb5b859d8be2a@epcas2p3.samsung.com>
2023-03-06 1:42 ` [PATCH] spi: s3c64xx: add no_cs description Jaewon Kim
2023-03-06 6:26 ` Krzysztof Kozlowski
2023-03-06 9:06 ` Andi Shyti [this message]
2023-03-30 13:40 ` Jaewon Kim
2023-03-30 14:46 ` Krzysztof Kozlowski
2023-03-31 1:07 ` Jaewon Kim
2023-03-30 19:59 ` 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=ZAWtMIDHGd+nBTA1@intel.intel \
--to=andi@etezian.org \
--cc=alim.akhtar@samsung.com \
--cc=jaewon02.kim@samsung.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@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).