From: Dan Carpenter <dan.carpenter@oracle.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Qing Wang <wangqing@vivo.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Vinod Koul <vkoul@kernel.org>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Kernel Janitors <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH V2] dma: dw-edma-pcie: switch from 'pci_' to 'dma_' API
Date: Tue, 9 Nov 2021 16:26:52 +0300 [thread overview]
Message-ID: <20211109132651.GK2026@kadam> (raw)
In-Reply-To: <20211109132137.GK2001@kadam>
On Tue, Nov 09, 2021 at 04:21:37PM +0300, Dan Carpenter wrote:
> drivers/dma/dw-edma/dw-edma-pcie.c:192 dw_edma_pcie_probe() info: return a literal instead of 'err'
>
> The idea of the Smatch check is that it's pretty easy to get "if (!ret)"
> and "if (ret)" transposed. It would show up in testing, of course, but
> the truth is that maintainers don't always have all the hardware they
> maintain.
>
> And the other idea is that "return 0;" is always more readable and
> intentional than "return ret;" where ret is zero.
So other style anti-patterns that this check finds are:
net/bluetooth/hci_sync.c
4489
4490 err = hci_start_scan_sync(hdev, LE_SCAN_ACTIVE, interval,
4491 hdev->le_scan_window_discovery,
4492 own_addr_type, filter_policy, filter_dup);
4493 if (!err)
4494 return err;
2) Success handling.
3) Making the last check special/opposite.
*sad face*
4495
4496 failed:
4497 /* Resume advertising if it was paused */
4498 if (use_ll_privacy(hdev))
regards,
dan carpenter
next prev parent reply other threads:[~2021-11-09 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 3:44 [PATCH V2] dma: dw-edma-pcie: switch from 'pci_' to 'dma_' API Qing Wang
2021-11-02 19:05 ` Christophe JAILLET
2021-11-09 13:21 ` Dan Carpenter
2021-11-09 13:26 ` Dan Carpenter [this message]
2021-11-09 21:11 ` Christophe JAILLET
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=20211109132651.GK2026@kadam \
--to=dan.carpenter@oracle.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dmaengine@vger.kernel.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.org \
--cc=wangqing@vivo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.