All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Miaoqian Lin <linmq006@gmail.com>
Cc: digetx@gmail.com, jckuo@nvidia.com, jonathanh@nvidia.com,
	kishon@ti.com, linux-kernel@vger.kernel.org,
	linux-phy@lists.infradead.org, linux-tegra@vger.kernel.org,
	vkoul@kernel.org
Subject: Re: [PATCH v2] phy: tegra: xusb: Fix return value of tegra_xusb_find_port_node function
Date: Mon, 13 Dec 2021 11:24:50 +0100	[thread overview]
Message-ID: <YbcfcpkwxCkeGP3f@orome> (raw)
In-Reply-To: <20211213020507.1458-1-linmq006@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 422 bytes --]

On Mon, Dec 13, 2021 at 02:05:07AM +0000, Miaoqian Lin wrote:
> callers of tegra_xusb_find_port_node() function only do NULL checking for
> the return value. return NULL instead of ERR_PTR(-ENOMEM) to keep
> consistent.
> 
> Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
> ---
>  drivers/phy/tegra/xusb.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Acked-by: Thierry Reding <treding@nvidia.com>

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 112 bytes --]

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Miaoqian Lin <linmq006@gmail.com>
Cc: digetx@gmail.com, jckuo@nvidia.com, jonathanh@nvidia.com,
	kishon@ti.com, linux-kernel@vger.kernel.org,
	linux-phy@lists.infradead.org, linux-tegra@vger.kernel.org,
	vkoul@kernel.org
Subject: Re: [PATCH v2] phy: tegra: xusb: Fix return value of tegra_xusb_find_port_node function
Date: Mon, 13 Dec 2021 11:24:50 +0100	[thread overview]
Message-ID: <YbcfcpkwxCkeGP3f@orome> (raw)
In-Reply-To: <20211213020507.1458-1-linmq006@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 422 bytes --]

On Mon, Dec 13, 2021 at 02:05:07AM +0000, Miaoqian Lin wrote:
> callers of tegra_xusb_find_port_node() function only do NULL checking for
> the return value. return NULL instead of ERR_PTR(-ENOMEM) to keep
> consistent.
> 
> Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
> ---
>  drivers/phy/tegra/xusb.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Acked-by: Thierry Reding <treding@nvidia.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-12-13 10:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-12  6:50 [PATCH] phy: tegra: xusb: Fix NULL vs IS_ERR_OR_NULL checking Miaoqian Lin
2021-12-12  6:50 ` Miaoqian Lin
2021-12-12 14:31 ` Dmitry Osipenko
2021-12-12 14:31   ` Dmitry Osipenko
2021-12-13  2:05   ` [PATCH v2] phy: tegra: xusb: Fix return value of tegra_xusb_find_port_node function Miaoqian Lin
2021-12-13  2:05     ` Miaoqian Lin
2021-12-13 10:24     ` Thierry Reding [this message]
2021-12-13 10:24       ` Thierry Reding
2021-12-14  7:37     ` Vinod Koul
2021-12-14  7:37       ` Vinod Koul

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=YbcfcpkwxCkeGP3f@orome \
    --to=thierry.reding@gmail.com \
    --cc=digetx@gmail.com \
    --cc=jckuo@nvidia.com \
    --cc=jonathanh@nvidia.com \
    --cc=kishon@ti.com \
    --cc=linmq006@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=vkoul@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 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.