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 1/3] staging: axis-fifo: simplify resource mapping
Date: Sun, 1 Mar 2026 00:55:17 +0000 [thread overview]
Message-ID: <20260301005519.2512706-1-objecting@objecting.org> (raw)
Use devm_platform_ioremap_resource() to simplify the code and remove the unused struct resource pointer.
Signed-off-by: Josh Law <objecting@objecting.org>
---
drivers/staging/axis-fifo/axis-fifo.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/axis-fifo/axis-fifo.c b/drivers/staging/axis-fifo/axis-fifo.c
index d83a0fd5b231..fc8e35696b31 100644
--- a/drivers/staging/axis-fifo/axis-fifo.c
+++ b/drivers/staging/axis-fifo/axis-fifo.c
@@ -450,7 +450,6 @@ static int axis_fifo_parse_dt(struct axis_fifo *fifo)
static int axis_fifo_probe(struct platform_device *pdev)
{
- struct resource *r_mem;
struct device *dev = &pdev->dev;
struct axis_fifo *fifo = NULL;
int rc = 0; /* error return value */
@@ -469,7 +468,7 @@ static int axis_fifo_probe(struct platform_device *pdev)
mutex_init(&fifo->read_lock);
mutex_init(&fifo->write_lock);
- fifo->base_addr = devm_platform_get_and_ioremap_resource(pdev, 0, &r_mem);
+ fifo->base_addr = devm_platform_ioremap_resource(pdev, 0);
if (IS_ERR(fifo->base_addr))
return PTR_ERR(fifo->base_addr);
--
2.43.0
next 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 Josh Law [this message]
2026-03-01 0:55 ` [PATCH 2/3] staging: axis-fifo: use dev_err_probe() for IRQ error handling Josh Law
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-1-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 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.