linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
Cc: linux-serial@vger.kernel.org, michal.simek@xilinx.com,
	jirislaby@kernel.org, git@xilinx.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/7] tty: xilinx_uartps: Add check for runtime_get_sync calls
Date: Thu, 5 May 2022 22:50:31 +0200	[thread overview]
Message-ID: <YnQ4lxfJUGe4TyFi@kroah.com> (raw)
In-Reply-To: <20220429081422.3630070-4-shubhrajyoti.datta@xilinx.com>

On Fri, Apr 29, 2022 at 01:44:18PM +0530, Shubhrajyoti Datta wrote:
> Add a check for the return value of runtime get_sync calls.
> 
> Addresses-Coverity: Event check_return.
> Signed-off-by: Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com>
> ---
>  drivers/tty/serial/xilinx_uartps.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/tty/serial/xilinx_uartps.c b/drivers/tty/serial/xilinx_uartps.c
> index 8f15fe24a0eb..868f4e587263 100644
> --- a/drivers/tty/serial/xilinx_uartps.c
> +++ b/drivers/tty/serial/xilinx_uartps.c
> @@ -1100,13 +1100,17 @@ static void cdns_uart_poll_put_char(struct uart_port *port, unsigned char c)
>  static void cdns_uart_pm(struct uart_port *port, unsigned int state,
>  		   unsigned int oldstate)
>  {
> +	int ret;
> +
>  	switch (state) {
>  	case UART_PM_STATE_OFF:
>  		pm_runtime_mark_last_busy(port->dev);
>  		pm_runtime_put_autosuspend(port->dev);
>  		break;
>  	default:
> -		pm_runtime_get_sync(port->dev);
> +		ret = pm_runtime_get_sync(port->dev);
> +		if (ret < 0)
> +			dev_err(port->dev, "Failed to enable clocks\n");

So you just ignore the error?  SHouldn't you propagate it back upward?

thanks,

greg k-h

  reply	other threads:[~2022-05-05 22:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29  8:14 [PATCH 0/7] tty: xilinx_uartps: fixes and improvements Shubhrajyoti Datta
2022-04-29  8:14 ` [PATCH 1/7] xilinx: Update copyright text to correct format Shubhrajyoti Datta
2022-04-29  8:14 ` [PATCH 2/7] tty: xilinx_uartps: Check the clk_enable return value Shubhrajyoti Datta
2022-05-05 20:50   ` Greg KH
2022-07-28 11:09     ` Datta, Shubhrajyoti
2022-07-28 11:48       ` Greg KH
2022-04-29  8:14 ` [PATCH 3/7] tty: xilinx_uartps: Add check for runtime_get_sync calls Shubhrajyoti Datta
2022-05-05 20:50   ` Greg KH [this message]
2022-05-10 11:53     ` Shubhrajyoti Datta
2022-04-29  8:14 ` [PATCH 4/7] tty: xilinx_uartps: Check clk_enable return value Shubhrajyoti Datta
2022-05-05 20:51   ` Greg KH
2022-04-29  8:14 ` [PATCH 5/7] tty: xilinx_uartps: Make the timeout unsigned Shubhrajyoti Datta
2022-05-05 20:54   ` Greg KH
2022-04-29  8:14 ` [PATCH 6/7] serial: uartps: Fix the ignore_status Shubhrajyoti Datta
2022-05-05 20:55   ` Greg KH
2022-04-29  8:14 ` [PATCH 7/7] serial: uartps: Prevent writes when the controller is disabled Shubhrajyoti Datta
2022-05-05 20:56   ` Greg KH
2022-05-05 20:48 ` [PATCH 0/7] tty: xilinx_uartps: fixes and improvements Greg KH
2022-05-10 11:54   ` Shubhrajyoti Datta

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=YnQ4lxfJUGe4TyFi@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=git@xilinx.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=shubhrajyoti.datta@xilinx.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;
as well as URLs for NNTP newsgroup(s).