From: phucduc.bui@gmail.com
To: Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
rafael@kernel.org, Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Diogo Ivo <diogo.ivo@tecnico.ulisboa.pt>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Cc: bui duc phuc <phucduc.bui@gmail.com>
Subject: [PATCH 3/3] usb: phy: Remove redundant OOM message
Date: Wed, 12 Aug 2026 11:28:41 +0700 [thread overview]
Message-ID: <20260812042842.15209-3-phucduc.bui@gmail.com> (raw)
In-Reply-To: <20260812042842.15209-1-phucduc.bui@gmail.com>
From: bui duc phuc <phucduc.bui@gmail.com>
Remove the dev_dbg() after a failed devres_alloc(). This is
consistent with checkpatch's OOM_MESSAGE convention: no error
message is needed after a kzalloc()-style allocation failure.
Signed-off-by: bui duc phuc <phucduc.bui@gmail.com>
---
drivers/usb/phy/phy.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/usb/phy/phy.c b/drivers/usb/phy/phy.c
index 5a9b9353f343..117a33fa9e91 100644
--- a/drivers/usb/phy/phy.c
+++ b/drivers/usb/phy/phy.c
@@ -534,10 +534,8 @@ struct usb_phy *devm_usb_get_phy_by_node(struct device *dev,
unsigned long flags;
ptr = devres_alloc(devm_usb_phy_release2, sizeof(*ptr), GFP_KERNEL);
- if (!ptr) {
- dev_dbg(dev, "failed to allocate memory for devres\n");
+ if (!ptr)
goto err0;
- }
spin_lock_irqsave(&phy_lock, flags);
--
2.43.0
prev parent reply other threads:[~2026-08-12 4:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 4:28 [PATCH 1/3] checkpatch: Add devres_alloc() to allocation functions phucduc.bui
2026-08-12 4:28 ` [PATCH 2/3] thermal: hwmon: Remove redundant OOM message phucduc.bui
2026-08-12 4:28 ` phucduc.bui [this message]
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=20260812042842.15209-3-phucduc.bui@gmail.com \
--to=phucduc.bui@gmail.com \
--cc=apw@canonical.com \
--cc=daniel.lezcano@kernel.org \
--cc=diogo.ivo@tecnico.ulisboa.pt \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
/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