From: Michal Simek <michal.simek@amd.com>
To: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>,
u-boot@lists.denx.de
Cc: jagan@amarulasolutions.com, git@amd.com
Subject: Re: [PATCH] spi: cadence_qspi: Add missing prototype for cadence_qspi_flash_reset
Date: Wed, 22 Jan 2025 16:58:51 +0100 [thread overview]
Message-ID: <7cc4bb17-389c-482d-9bbc-dbdc563a1627@amd.com> (raw)
In-Reply-To: <20250122135334.1201562-1-venkatesh.abbarapu@amd.com>
On 1/22/25 14:53, Venkatesh Yadav Abbarapu wrote:
> Add missing prototype to fix the sparse warning,
> warning: no previous prototype for 'cadence_qspi_flash_reset'
> [-Wmissing-prototypes].
>
> Fixes: 6d234a79e9 ("cadence_qspi: Refactor the flash reset functionality")
> Signed-off-by: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>
> ---
> drivers/spi/cadence_qspi.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/spi/cadence_qspi.h b/drivers/spi/cadence_qspi.h
> index 693474a2871..1f9125cd239 100644
> --- a/drivers/spi/cadence_qspi.h
> +++ b/drivers/spi/cadence_qspi.h
> @@ -307,7 +307,7 @@ int cadence_qspi_apb_dma_read(struct cadence_spi_priv *priv,
> const struct spi_mem_op *op);
> int cadence_qspi_apb_wait_for_dma_cmplt(struct cadence_spi_priv *priv);
> int cadence_qspi_apb_exec_flash_cmd(void *reg_base, unsigned int reg);
> -int cadence_qspi_versal_flash_reset(struct udevice *dev);
> +int cadence_qspi_flash_reset(struct udevice *dev);
> ofnode cadence_qspi_get_subnode(struct udevice *dev);
> void cadence_qspi_apb_enable_linear_mode(bool enable);
>
Applied.
M
prev parent reply other threads:[~2025-01-22 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 13:53 [PATCH] spi: cadence_qspi: Add missing prototype for cadence_qspi_flash_reset Venkatesh Yadav Abbarapu
2025-01-22 15:58 ` Michal Simek [this message]
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=7cc4bb17-389c-482d-9bbc-dbdc563a1627@amd.com \
--to=michal.simek@amd.com \
--cc=git@amd.com \
--cc=jagan@amarulasolutions.com \
--cc=u-boot@lists.denx.de \
--cc=venkatesh.abbarapu@amd.com \
/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