From: Josh Law <hlcj1234567@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Josh Law <objecting@objecting.org>
Subject: [PATCH 2/3] staging: axis-fifo: use dev_err_probe() for IRQ error handling
Date: Sun, 1 Mar 2026 00:55:18 +0000 [thread overview]
Message-ID: <20260301005519.2512706-2-objecting@objecting.org> (raw)
In-Reply-To: <20260301005519.2512706-1-objecting@objecting.org>
Simplify the error handling in the probe function by using dev_err_probe() instead of dev_err() when devm_request_irq() fails.
Signed-off-by: Josh Law <objecting@objecting.org>
---
drivers/staging/axis-fifo/axis-fifo.c | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/axis-fifo/axis-fifo.c b/drivers/staging/axis-fifo/axis-fifo.c
index fc8e35696b31..28268881cda2 100644
--- a/drivers/staging/axis-fifo/axis-fifo.c
+++ b/drivers/staging/axis-fifo/axis-fifo.c
@@ -484,11 +484,9 @@ static int axis_fifo_probe(struct platform_device *pdev)
rc = devm_request_irq(fifo->dt_device, irq, &axis_fifo_irq, 0,
DRIVER_NAME, fifo);
- if (rc) {
- dev_err(fifo->dt_device, "couldn't allocate interrupt %i\n",
- irq);
- return rc;
- }
+ if (rc)
+ return dev_err_probe(fifo->dt_device, rc,
+ "couldn't allocate interrupt %i\n", irq);
fifo->id = ida_alloc(&axis_fifo_ida, GFP_KERNEL);
if (fifo->id < 0)
--
2.43.0
next prev parent reply other threads:[~2026-03-01 0:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 0:55 [PATCH 1/3] staging: axis-fifo: simplify resource mapping Josh Law
2026-03-01 0:55 ` Josh Law [this message]
2026-03-01 0:55 ` [PATCH 3/3] staging: axis-fifo: improve IRQ handler Josh Law
2026-03-02 9:19 ` [PATCH 1/3] staging: axis-fifo: simplify resource mapping Dan Carpenter
2026-03-02 21:31 ` Ethan Tidmore
2026-03-02 21:36 ` Josh Law
2026-03-02 21:38 ` Ethan Tidmore
2026-03-02 21:40 ` Josh Law
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=20260301005519.2512706-2-objecting@objecting.org \
--to=hlcj1234567@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=objecting@objecting.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