From: Thierry Reding <thierry.reding@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 4/4] memory: tegra-mc: Use %pe format
Date: Fri, 27 Feb 2026 12:56:29 +0100 [thread overview]
Message-ID: <aaGGZrjCqAGrhz8P@orome> (raw)
In-Reply-To: <20260226-memory-simplify-v1-4-ccb94f378628@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
On Thu, Feb 26, 2026 at 09:35:27PM +0100, Krzysztof Kozlowski wrote:
> Make code printing pointer error value a bit simpler and fix coccinelle
> suggestion:
>
> tegra/mc.c:975:4-11: WARNING: Consider using %pe to print PTR_ERR()
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> ---
> drivers/memory/tegra/mc.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-02-27 11:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 20:35 [PATCH 0/4] memory: Few code cleanups Krzysztof Kozlowski
2026-02-26 20:35 ` [PATCH 1/4] memory: renesas-rpc-if: Simplify printing PTR_ERR with dev_err_probe Krzysztof Kozlowski
2026-02-26 20:35 ` [PATCH 2/4] memory: tegra-mc: Drop tegra_mc_setup_latency_allowance() return value Krzysztof Kozlowski
2026-02-27 11:55 ` Thierry Reding
2026-02-26 20:35 ` [PATCH 3/4] memory: tegra-mc: Simplify printing PTR_ERR with dev_err_probe Krzysztof Kozlowski
2026-02-27 11:56 ` Thierry Reding
2026-02-26 20:35 ` [PATCH 4/4] memory: tegra-mc: Use %pe format Krzysztof Kozlowski
2026-02-27 11:56 ` Thierry Reding [this message]
2026-03-05 11:57 ` [PATCH 0/4] memory: Few code cleanups Krzysztof Kozlowski
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=aaGGZrjCqAGrhz8P@orome \
--to=thierry.reding@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.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