public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: Shawn Lin <shawn.lin@rock-chips.com>, Mark Brown <broonie@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-spi@vger.kernel.org>,
	Doug Anderson <dianders@chromium.org>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] spi: rockchip: fix warning of static check
Date: Tue, 22 Mar 2016 15:00:23 +0200	[thread overview]
Message-ID: <56F141E7.5030303@mentor.com> (raw)
In-Reply-To: <56F140E4.8010906@mentor.com>

On 22.03.2016 14:56, Vladimir Zapolskiy wrote:
> Hi Shawn,
> 
> On 22.03.2016 13:36, Shawn Lin wrote:
>> Let's improve the check with -EPROBE_DEFER, otherwise
>> we may pass on null pointer to PTR_ERR. That causes the
>> static checker warning: passing zero to 'PTR_ERR'.
>>
>> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
>> Cc: Doug Anderson <dianders@chromium.org>
>> Cc: Dan Carpenter <dan.carpenter@oracle.com>
>> Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com>
>> ---
>>
>>  drivers/spi/spi-rockchip.c | 10 +++++++---
>>  1 file changed, 7 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/spi/spi-rockchip.c b/drivers/spi/spi-rockchip.c
>> index bfeb0d4..2cb36d9 100644
>> --- a/drivers/spi/spi-rockchip.c
>> +++ b/drivers/spi/spi-rockchip.c
>> @@ -726,20 +726,24 @@ static int rockchip_spi_probe(struct platform_device *pdev)
>>  	rs->dma_tx.ch = dma_request_slave_channel(rs->dev, "tx");
>>  	if (IS_ERR_OR_NULL(rs->dma_tx.ch)) {
>>  		/* Check tx to see if we need defer probing driver */
>> -		if (PTR_ERR(rs->dma_tx.ch) == -EPROBE_DEFER) {
>> +		if (rs->dma_tx.ch == ERR_PTR(-EPROBE_DEFER)) {
> 
> won't it be easier to change dma_request_slave_channel() to
> dma_request_chan() or dma_request_slave_channel_reason() and replace strange
> IS_ERR_OR_NULL() check with IS_ERR() one?
> 
> AFAIU that's almost what has been suggested by Doug and it is a better
> fix than this one published.
> 
> At the moment check for IS_ERR_OR_NULL() is too aggressive and quite
> confusing, because dma_request_slave_channel() never returns NULL.

Sorry for a typo, never returns IS_ERR() of course.

>>  			ret = -EPROBE_DEFER;
>>  			goto err_get_fifo_len;
>>  		}
>>  		dev_warn(rs->dev, "Failed to request TX DMA channel\n");
>> +		rs->dma_tx.ch = NULL;
>>  	}
>>  
>>  	rs->dma_rx.ch = dma_request_slave_channel(rs->dev, "rx");
>> -	if (!rs->dma_rx.ch) {
>> -		if (rs->dma_tx.ch) {
>> +	if (IS_ERR_OR_NULL(rs->dma_rx.ch)) {
>> +		if (rs->dma_tx.ch == ERR_PTR(-EPROBE_DEFER)) {
> 
> Same as above.
> 
>>  			dma_release_channel(rs->dma_tx.ch);
>>  			rs->dma_tx.ch = NULL;
>> +			ret = -EPROBE_DEFER;
>> +			goto err_get_fifo_len;
>>  		}
>>  		dev_warn(rs->dev, "Failed to request RX DMA channel\n");
>> +		rs->dma_rx.ch = NULL;
>>  	}
>>  
>>  	if (rs->dma_tx.ch && rs->dma_rx.ch) {
>>
> 

--
With best wishes,
Vladimir

  reply	other threads:[~2016-03-22 13:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 11:36 [PATCH] spi: rockchip: fix warning of static check Shawn Lin
2016-03-22 12:56 ` Vladimir Zapolskiy
2016-03-22 13:00   ` Vladimir Zapolskiy [this message]
2016-03-22 16:23 ` Doug Anderson

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=56F141E7.5030303@mentor.com \
    --to=vladimir_zapolskiy@mentor.com \
    --cc=broonie@kernel.org \
    --cc=dan.carpenter@oracle.com \
    --cc=dianders@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=shawn.lin@rock-chips.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