From: Michal Simek <michal.simek@amd.com>
To: Min-Hua Chen <minhuadotchen@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] serial: xilinx_uartps: make cdns_rs485_supported static
Date: Fri, 6 Sep 2024 09:05:01 +0200 [thread overview]
Message-ID: <33cb57cd-200b-48a7-9028-3f6bf46b4dde@amd.com> (raw)
In-Reply-To: <20240905231930.343759-1-minhuadotchen@gmail.com>
On 9/6/24 01:19, Min-Hua Chen wrote:
> make cdns_rs485_supported static to fix the following sparse
> warning:
>
> drivers/tty/serial/xilinx_uartps.c:222:21: sparse: warning:
> symbol 'cdns_rs485_supported' was not declared. Should it be static?
>
> Signed-off-by: Min-Hua Chen <minhuadotchen@gmail.com>
> ---
> drivers/tty/serial/xilinx_uartps.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/tty/serial/xilinx_uartps.c b/drivers/tty/serial/xilinx_uartps.c
> index 2acfcea403ce..777392914819 100644
> --- a/drivers/tty/serial/xilinx_uartps.c
> +++ b/drivers/tty/serial/xilinx_uartps.c
> @@ -219,7 +219,7 @@ struct cdns_platform_data {
> u32 quirks;
> };
>
> -struct serial_rs485 cdns_rs485_supported = {
> +static struct serial_rs485 cdns_rs485_supported = {
> .flags = SER_RS485_ENABLED | SER_RS485_RTS_ON_SEND |
> SER_RS485_RTS_AFTER_SEND,
> .delay_rts_before_send = 1,
This has been applied already as commit 68c5efd9dca ("serial: xilinx_uartps:
Make cdns_rs485_supported static").
You can also see it here
https://lore.kernel.org/r/20240819120107.3884973-1-ruanjinjie@huawei.com
Thanks,
Michal
next prev parent reply other threads:[~2024-09-06 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 23:19 Min-Hua Chen
2024-09-06 7:05 ` Michal Simek [this message]
2024-09-06 9:03 ` Min-Hua Chen
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=33cb57cd-200b-48a7-9028-3f6bf46b4dde@amd.com \
--to=michal.simek@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=minhuadotchen@gmail.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
all inboxes | Powered by JetHome®