From: Johan Hovold <johan@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrey Smirnov <andrew.smirnov@gmail.com>
Subject: Re: [PATCH] tty: serdev: fix serdev_device_write return value
Date: Tue, 2 May 2017 11:25:27 +0200 [thread overview]
Message-ID: <20170502092527.GC2973@localhost> (raw)
In-Reply-To: <20170502001714.11576-1-robh@kernel.org>
On Mon, May 01, 2017 at 07:17:14PM -0500, Rob Herring wrote:
> Commit 6fe729c4bdae ("serdev: Add serdev_device_write subroutine")
> provides a compatibility wrapper for the existing
> serdev_device_write_buf, but it fails to return the number of bytes
> written causing users to timeout.
So this would also be fixed for serdev_device_write_buf() by Stefan
Wahren's patch restoring that function implementation, but returning the
amount written is perhaps desirable also for blocking writes for
consistency reasons.
> Fixes: 6fe729c4bdae ("serdev: Add serdev_device_write subroutine")
> Cc: Andrey Smirnov <andrew.smirnov@gmail.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---
> drivers/tty/serdev/core.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/tty/serdev/core.c b/drivers/tty/serdev/core.c
> index 433de5ea9b02..ccfe56355c4f 100644
> --- a/drivers/tty/serdev/core.c
> +++ b/drivers/tty/serdev/core.c
> @@ -127,7 +127,7 @@ int serdev_device_write(struct serdev_device *serdev,
> unsigned long timeout)
> {
> struct serdev_controller *ctrl = serdev->ctrl;
> - int ret;
> + int ret, wr_cnt = 0;
>
> if (!ctrl || !ctrl->ops->write_buf ||
> (timeout && !serdev->ops->write_wakeup))
> @@ -143,12 +143,13 @@ int serdev_device_write(struct serdev_device *serdev,
>
> buf += ret;
> count -= ret;
> + wr_cnt += ret;
>
> } while (count &&
> (timeout = wait_for_completion_timeout(&serdev->write_comp,
> timeout)));
>
> mutex_unlock(&serdev->write_lock);
> - return ret < 0 ? ret : (count ? -ETIMEDOUT : 0);
> + return ret < 0 ? ret : (count ? -ETIMEDOUT : wr_cnt);
That's some nasty use of the ternary operator. Ditching it completely
would be more readable.
if (ret < 0)
return ret;
if (count)
return -ETIMEDOUT;
return wr_count;
and here wr_count is the value of count passed to the function (and
could just be stored on entry instead).
> }
> EXPORT_SYMBOL_GPL(serdev_device_write);
Thanks,
Johan
next prev parent reply other threads:[~2017-05-02 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 0:17 [PATCH] tty: serdev: fix serdev_device_write return value Rob Herring
2017-05-02 9:25 ` Johan Hovold [this message]
2017-05-02 12:30 ` Rob Herring
2017-05-03 17:44 ` Andy Shevchenko
2017-05-03 18:06 ` Greg Kroah-Hartman
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=20170502092527.GC2973@localhost \
--to=johan@kernel.org \
--cc=andrew.smirnov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh@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