From: Greg KH <gregkh@linuxfoundation.org>
To: Zhou jie <zhoujie@nfschina.com>
Cc: johan@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@nfschina.com
Subject: Re: [PATCH] usb/serial:Modify the return value to void
Date: Thu, 11 Aug 2022 10:21:20 +0200 [thread overview]
Message-ID: <YvS8AK9apa7tnYOz@kroah.com> (raw)
In-Reply-To: <20220811070358.5472-1-zhoujie@nfschina.com>
On Thu, Aug 11, 2022 at 03:03:58PM +0800, Zhou jie wrote:
> Modify the return value to void,The return value is not used elsewhere.
>
> Signed-off-by: Zhou jie <zhoujie@nfschina.com>
> ---
> drivers/usb/serial/mos7720.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/usb/serial/mos7720.c b/drivers/usb/serial/mos7720.c
> index 1e12b5f30dcc..ddb3a2d0f819 100644
> --- a/drivers/usb/serial/mos7720.c
> +++ b/drivers/usb/serial/mos7720.c
> @@ -239,13 +239,12 @@ static int read_mos_reg(struct usb_serial *serial, unsigned int serial_portnum,
>
> #ifdef CONFIG_USB_SERIAL_MOS7715_PARPORT
>
> -static inline int mos7715_change_mode(struct mos7715_parport *mos_parport,
> +static inline void mos7715_change_mode(struct mos7715_parport *mos_parport,
> enum mos7715_pp_modes mode)
> {
> mos_parport->shadowECR = mode;
> write_mos_reg(mos_parport->serial, dummy, MOS7720_ECR,
> mos_parport->shadowECR);
> - return 0;
Why not check the return value of write_mos_reg() and properly handle
the error that can give you instead of ignoring it?
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-11 8:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 7:03 Zhou jie
2022-08-11 8:21 ` Greg KH [this message]
2022-08-11 8:42 ` Zhou jie
2022-08-11 8:42 ` [PATCH v2] usb/serial:Repair function return value Zhou jie
2022-08-11 8:51 ` Greg KH
2022-08-11 9:05 ` Zhou jie
2022-08-11 9:12 ` Greg KH
2022-08-11 9:05 ` Greg KH
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=YvS8AK9apa7tnYOz@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=kernel@nfschina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=zhoujie@nfschina.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®