public inbox for linux-phy@lists.infradead.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	Sven Peter <sven@kernel.org>, Janne Grunau <j@jannau.net>,
	Neal Gompa <neal@gompa.dev>, Vinod Koul <vkoul@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 3/3] phy: qcom: qmp-usbc: Simplify check for non-NULL pointer
Date: Mon, 16 Feb 2026 12:33:05 +0100	[thread overview]
Message-ID: <5647539c-de68-40c8-8dd0-bf078a086696@oss.qualcomm.com> (raw)
In-Reply-To: <20260216110413.159994-6-krzysztof.kozlowski@oss.qualcomm.com>

On 2/16/26 12:04 PM, Krzysztof Kozlowski wrote:
> Pointers should not use explicit '0' comparison, so just use standard
> evaluation as non-NULL:
> 
>   phy-qcom-qmp-usbc.c:1682:31: warning: Using plain integer as NULL pointer
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> ---

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Konrad

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

  reply	other threads:[~2026-02-16 11:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16 11:04 [PATCH 1/3] phy: apple: atc: Make atcphy_dwc3_reset_ops variable static Krzysztof Kozlowski
2026-02-16 11:04 ` [PATCH 2/3] phy: marvell: mmp3-hsic: Avoid re-casting __iomem Krzysztof Kozlowski
2026-02-16 11:04 ` [PATCH 3/3] phy: qcom: qmp-usbc: Simplify check for non-NULL pointer Krzysztof Kozlowski
2026-02-16 11:33   ` Konrad Dybcio [this message]
2026-02-16 14:58   ` Abel Vesa
2026-02-24  7:47   ` Dmitry Baryshkov
2026-02-24  7:57 ` [PATCH 1/3] phy: apple: atc: Make atcphy_dwc3_reset_ops variable static Janne Grunau
2026-02-27 15:29 ` 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=5647539c-de68-40c8-8dd0-bf078a086696@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=asahi@lists.linux.dev \
    --cc=j@jannau.net \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=neal@gompa.dev \
    --cc=neil.armstrong@linaro.org \
    --cc=p.zabel@pengutronix.de \
    --cc=sven@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox