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 v2 0/3] usb: Use %pe to print error pointers
Date: Sat, 01 Aug 2026 17:59:49 +0530 [thread overview]
Message-ID: <20260801-usb-ptr_err_patchset-v2-0-1698e298c1e3@gmail.com> (raw)
Replace PTR_ERR() in format strings with
%pe format specifier across the USB subsystem. %pe prints
symbolic error names (e.g., -ENOMEM) instead of
raw numbers (e.g., -12), making error logs more readable.
These patches fix coccinelle reported warning: "Consider
using %pe to print PTR_ERR()" in usb subsystem.
The patches are grouped by subsystem:
1/3 - chipidea
2/3 - miscellaneous USB drivers
3/3 - typec
All patches are compile-tested on x86_64. Please let me know if
any more testing is needed for any patch.
Signed-off-by: Subasri S <subasris1210@gmail.com>
---
Changes in v2:
- Remove "This patch" phrasing from the commit message body.
- Trim redundant Coccinelle warning outputs in the commit log to keep only one.
- Clean up multi-line dev_err() statements into single lines.
- Link to v1: https://lore.kernel.org/r/20260719-usb-ptr_err_patchset-v1-0-85f7f2e4fefb@gmail.com
---
Subasri S (3):
usb: chipidea: Use %pe to print error pointers
usb: misc: Use %pe to print error pointers
usb: typec: Use %pe to print error pointers
drivers/usb/atm/usbatm.c | 4 ++--
drivers/usb/chipidea/ci_hdrc_imx.c | 12 ++++++------
drivers/usb/chipidea/core.c | 4 ++--
drivers/usb/core/hub.c | 3 +--
drivers/usb/dwc2/pci.c | 3 +--
drivers/usb/gadget/function/u_serial.c | 4 ++--
drivers/usb/misc/usb3503.c | 3 +--
drivers/usb/typec/mux/pi3usb30532.c | 6 ++----
drivers/usb/typec/tcpm/tcpm.c | 2 +-
drivers/usb/typec/wusb3801.c | 4 ++--
10 files changed, 20 insertions(+), 25 deletions(-)
---
base-commit: a13c140cc289c0b7b3770bce5b3ad42ab35074aa
change-id: 20260718-usb-ptr_err_patchset-7c5d1547bee7
Best regards,
--
Subasri S <subasris1210@gmail.com>
next reply other threads:[~2026-08-01 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 12:29 Subasri S [this message]
2026-08-01 12:29 ` [PATCH v2 1/3] usb: chipidea: Use %pe to print error pointers Subasri S
2026-08-01 12:29 ` [PATCH v2 2/3] usb: misc: " Subasri S
2026-08-01 12:29 ` [PATCH v2 3/3] usb: typec: " Subasri S
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=20260801-usb-ptr_err_patchset-v2-0-1698e298c1e3@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.