From: Arnd Bergmann <arnd@kernel.org>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Wang Qing <wangqing@vivo.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Samuel Zou <zou_wei@huawei.com>,
Kurt Kanzenbach <kurt@linutronix.de>,
Richard Cochran <richardcochran@gmail.com>,
Networking <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net/ethernet: update ret when ptp_clock is ERROR
Date: Fri, 6 Nov 2020 13:11:13 +0100 [thread overview]
Message-ID: <CAK8P3a0Dce3dYER0oJ+2FcV8UbJqCaAv7zSS6JZBdb6ewfnE7g@mail.gmail.com> (raw)
In-Reply-To: <fd46310f-0b4e-ac8b-b187-98438ee6bb60@ti.com>
On Fri, Nov 6, 2020 at 12:35 PM Grygorii Strashko
<grygorii.strashko@ti.com> wrote:
> On 06/11/2020 09:56, Wang Qing wrote:
> > +++ b/drivers/net/ethernet/ti/am65-cpts.c
> > @@ -1001,8 +1001,7 @@ struct am65_cpts *am65_cpts_create(struct device *dev, void __iomem *regs,
>
> there is
> cpts->ptp_clock = ptp_clock_register(&cpts->ptp_info, cpts->dev);
>
>
> > if (IS_ERR_OR_NULL(cpts->ptp_clock)) {
>
> And ptp_clock_register() can return NULL only if PTP support is disabled.
> In which case, we should not even get here.
>
> So, I'd propose to s/IS_ERR_OR_NULL/IS_ERR above,
> and just assign ret = PTR_ERR(cpts->ptp_clock) here.
Right, using IS_ERR_OR_NULL() is almost ever a mistake, either
from misunderstanding the interface, or from a badly designed
interface that needs to be changed.
Arnd
next prev parent reply other threads:[~2020-11-06 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 7:56 [PATCH] net/ethernet: update ret when ptp_clock is ERROR Wang Qing
2020-11-06 11:34 ` Grygorii Strashko
2020-11-06 12:11 ` Arnd Bergmann [this message]
2020-11-06 12:58 ` Kurt Kanzenbach
2020-11-06 14:48 ` Grygorii Strashko
2020-11-07 15:07 ` Richard Cochran
2020-11-07 15:08 ` Richard Cochran
2020-11-11 13:03 ` Grygorii Strashko
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=CAK8P3a0Dce3dYER0oJ+2FcV8UbJqCaAv7zSS6JZBdb6ewfnE7g@mail.gmail.com \
--to=arnd@kernel.org \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=wangqing@vivo.com \
--cc=zou_wei@huawei.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;
as well as URLs for NNTP newsgroup(s).