From: Subasri S <subasris1210@gmail.com>
To: Peter Chen <peter.chen@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Duncan Sands <duncan.sands@free.fr>,
Chas Williams <3chas3@gmail.com>,
Minas Harutyunyan <hminas@synopsys.com>,
Hans de Goede <hansg@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Badhri Jagan Sridharan <badhri@google.com>
Cc: linux-usb@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-atm-general@lists.sourceforge.net, netdev@vger.kernel.org,
Subasri S <subasris1210@gmail.com>
Subject: [PATCH RESEND v2 3/3] usb: typec: Use %pe to print error pointers
Date: Tue, 13 Oct 2026 08:25:39 +0530 [thread overview]
Message-ID: <20261013-usb-ptr_err_patchset-v2-3-f83351b3fc3d@gmail.com> (raw)
In-Reply-To: <20261013-usb-ptr_err_patchset-v2-0-f83351b3fc3d@gmail.com>
Use the %pe format specifier instead of %ld with PTR_ERR() for printing
error pointers in various typec drivers. This prints symbolic
error names (e.g.-ENOMEM) instead of errno numbers (e.g. -12),
making error logs more readable.
Fix coccinelle reported warning:
WARNING: Consider using %pe to print PTR_ERR()
Compile tested only.
Reviewed-by: Badhri Jagan Sridharan <badhri@google.com>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Reviewed-by: Frank Li <Frank.Li@nxp.com>
Signed-off-by: Subasri S <subasris1210@gmail.com>
---
drivers/usb/typec/mux/pi3usb30532.c | 6 ++----
drivers/usb/typec/tcpm/tcpm.c | 2 +-
drivers/usb/typec/wusb3801.c | 4 ++--
3 files changed, 5 insertions(+), 7 deletions(-)
diff --git a/drivers/usb/typec/mux/pi3usb30532.c b/drivers/usb/typec/mux/pi3usb30532.c
index 985683fe49e9..b32f4c433de9 100644
--- a/drivers/usb/typec/mux/pi3usb30532.c
+++ b/drivers/usb/typec/mux/pi3usb30532.c
@@ -139,8 +139,7 @@ static int pi3usb30532_probe(struct i2c_client *client)
pi->sw = typec_switch_register(dev, &sw_desc);
if (IS_ERR(pi->sw)) {
- dev_err(dev, "Error registering typec switch: %ld\n",
- PTR_ERR(pi->sw));
+ dev_err(dev, "Error registering typec switch: %pe\n", pi->sw);
return PTR_ERR(pi->sw);
}
@@ -151,8 +150,7 @@ static int pi3usb30532_probe(struct i2c_client *client)
pi->mux = typec_mux_register(dev, &mux_desc);
if (IS_ERR(pi->mux)) {
typec_switch_unregister(pi->sw);
- dev_err(dev, "Error registering typec mux: %ld\n",
- PTR_ERR(pi->mux));
+ dev_err(dev, "Error registering typec mux: %pe\n", pi->mux);
return PTR_ERR(pi->mux);
}
diff --git a/drivers/usb/typec/tcpm/tcpm.c b/drivers/usb/typec/tcpm/tcpm.c
index 89eec20a2064..ad10470ea73b 100644
--- a/drivers/usb/typec/tcpm/tcpm.c
+++ b/drivers/usb/typec/tcpm/tcpm.c
@@ -4796,7 +4796,7 @@ static void tcpm_typec_connect(struct tcpm_port *port)
port->partner_desc.accessory = TYPEC_ACCESSORY_NONE;
partner = typec_register_partner(port->typec_port, &port->partner_desc);
if (IS_ERR(partner)) {
- dev_err(port->dev, "Failed to register partner (%ld)\n", PTR_ERR(partner));
+ dev_err(port->dev, "Failed to register partner (%pe)\n", partner);
return;
}
diff --git a/drivers/usb/typec/wusb3801.c b/drivers/usb/typec/wusb3801.c
index 6062875fb04a..86d13ab41670 100644
--- a/drivers/usb/typec/wusb3801.c
+++ b/drivers/usb/typec/wusb3801.c
@@ -277,8 +277,8 @@ static void wusb3801_hw_update(struct wusb3801 *wusb3801)
if (partner_type != WUSB3801_STAT_PARTNER_STANDBY) {
wusb3801->partner = typec_register_partner(port, &desc);
if (IS_ERR(wusb3801->partner))
- dev_err(dev, "Failed to register partner: %ld\n",
- PTR_ERR(wusb3801->partner));
+ dev_err(dev, "Failed to register partner: %pe\n",
+ wusb3801->partner);
}
data_role = pwr_role == TYPEC_SOURCE ? TYPEC_HOST : TYPEC_DEVICE;
--
2.43.0
next prev parent reply other threads:[~2026-10-13 2:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 2:55 [PATCH RESEND v2 0/3] usb: Use %pe to print error pointers Subasri S
2026-10-13 2:55 ` [PATCH RESEND v2 1/3] usb: chipidea: " Subasri S
2026-10-13 3:02 ` sashiko-bot
2026-10-13 2:55 ` [PATCH RESEND v2 2/3] usb: misc: " Subasri S
2026-10-13 3:02 ` sashiko-bot
2026-10-13 2:55 ` Subasri S [this message]
2026-10-13 3:02 ` [PATCH RESEND v2 3/3] usb: typec: " sashiko-bot
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=20261013-usb-ptr_err_patchset-v2-3-f83351b3fc3d@gmail.com \
--to=subasris1210@gmail.com \
--cc=3chas3@gmail.com \
--cc=Frank.Li@nxp.com \
--cc=badhri@google.com \
--cc=duncan.sands@free.fr \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=hminas@synopsys.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.chen@kernel.org \
--cc=s.hauer@pengutronix.de \
/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.