From: Philippe CORNU <philippe.cornu@st.com>
To: Andrzej Hajda <a.hajda@samsung.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Gustavo Padovan <gustavo@padovan.org>,
Sean Paul <seanpaul@chromium.org>,
David Airlie <airlied@linux.ie>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Archit Taneja <architt@codeaurora.org>,
Brian Norris <briannorris@chromium.org>,
Benjamin Gaignard <benjamin.gaignard@linaro.org>,
Yannick FERTRE <yannick.fertre@st.com>,
Vincent ABRIOU <vincent.abriou@st.com>,
Alexandre TORGUE <alexandre.torgue@st.com>
Subject: Re: [PATCH] drm/dsi: Fix improper use of mipi_dsi_device_transfer() return value
Date: Mon, 15 Jan 2018 13:42:00 +0000 [thread overview]
Message-ID: <4ee77a69-321e-11d0-77fa-4adb9f6ef3d1@st.com> (raw)
In-Reply-To: <e3936ab6-742a-de54-1d43-510134c3fe65@samsung.com>
Hi Andrzej,
On 01/15/2018 10:12 AM, Andrzej Hajda wrote:
> On 12.01.2018 15:48, Philippe Cornu wrote:
>> The function mipi_dsi_device_transfer() returns the number of transmitted
>> or received bytes on success or a negative error code on failure.
>>
>> The functions mipi_dsi_shutdown_peripheral(), mipi_dsi_turn_on_peripheral() &
>> mipi_dsi_set_maximum_return_packet_size() use improperly this returned
>> value in case of success: 0 should be returned instead of the number of
>> transmitted bytes.
>>
>> Signed-off-by: Philippe Cornu <philippe.cornu@st.com>
>
> I guess, the best would be to create and use some helper similar to
> PTR_ERR_OR_ZERO,
> but this is also OK.
>
Many thanks for your comment and review.
Before sending this patch, I searched for a better way to write these
few lines, including searching for such macros but I did not find
anything (pointers are largely covered but simple integers are not).
If someone has a better solution (with macros or otherwise), I am happy
to learn/implement it.
Many thanks,
Philippe : )
> Reviewed-by: Andrzej Hajda <a.hajda@samsung.com>
>
> --
> Regards
> Andrzej
>
>> ---
>> drivers/gpu/drm/drm_mipi_dsi.c | 9 ++++++---
>> 1 file changed, 6 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_mipi_dsi.c b/drivers/gpu/drm/drm_mipi_dsi.c
>> index 4b47226b90d4..bc73b7f5b9fc 100644
>> --- a/drivers/gpu/drm/drm_mipi_dsi.c
>> +++ b/drivers/gpu/drm/drm_mipi_dsi.c
>> @@ -498,8 +498,9 @@ int mipi_dsi_shutdown_peripheral(struct mipi_dsi_device *dsi)
>> .tx_buf = (u8 [2]) { 0, 0 },
>> .tx_len = 2,
>> };
>> + int ret = mipi_dsi_device_transfer(dsi, &msg);
>>
>> - return mipi_dsi_device_transfer(dsi, &msg);
>> + return (ret < 0) ? ret : 0;
>> }
>> EXPORT_SYMBOL(mipi_dsi_shutdown_peripheral);
>>
>> @@ -517,8 +518,9 @@ int mipi_dsi_turn_on_peripheral(struct mipi_dsi_device *dsi)
>> .tx_buf = (u8 [2]) { 0, 0 },
>> .tx_len = 2,
>> };
>> + int ret = mipi_dsi_device_transfer(dsi, &msg);
>>
>> - return mipi_dsi_device_transfer(dsi, &msg);
>> + return (ret < 0) ? ret : 0;
>> }
>> EXPORT_SYMBOL(mipi_dsi_turn_on_peripheral);
>>
>> @@ -541,8 +543,9 @@ int mipi_dsi_set_maximum_return_packet_size(struct mipi_dsi_device *dsi,
>> .tx_len = sizeof(tx),
>> .tx_buf = tx,
>> };
>> + int ret = mipi_dsi_device_transfer(dsi, &msg);
>>
>> - return mipi_dsi_device_transfer(dsi, &msg);
>> + return (ret < 0) ? ret : 0;
>> }
>> EXPORT_SYMBOL(mipi_dsi_set_maximum_return_packet_size);
>>
>
>
next prev parent reply other threads:[~2018-01-15 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180112144953epcas2p3046bd1b5cb6de9a616c5e6688cee97b4@epcas2p3.samsung.com>
2018-01-12 14:48 ` Philippe Cornu
2018-01-15 9:12 ` Andrzej Hajda
2018-01-15 13:42 ` Philippe CORNU [this message]
2018-01-16 22:23 ` Sean Paul
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=4ee77a69-321e-11d0-77fa-4adb9f6ef3d1@st.com \
--to=philippe.cornu@st.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=alexandre.torgue@st.com \
--cc=architt@codeaurora.org \
--cc=benjamin.gaignard@linaro.org \
--cc=briannorris@chromium.org \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanpaul@chromium.org \
--cc=vincent.abriou@st.com \
--cc=yannick.fertre@st.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®