From: Damien Le Moal <dlemoal@kernel.org>
To: Rosen Penev <rosenp@gmail.com>, linux-ide@vger.kernel.org
Cc: Niklas Cassel <cassel@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
open list <linux-kernel@vger.kernel.org>,
"open list:CLANG/LLVM BUILD SUPPORT:Keyword:b(?i:clang|llvm)b"
<llvm@lists.linux.dev>
Subject: Re: [PATCH] ata: sata_highbank: use devm_platform_ioremap_resource
Date: Sat, 18 Jul 2026 12:06:16 +0900 [thread overview]
Message-ID: <314972c4-8f66-46d3-bc09-1e05db700688@kernel.org> (raw)
In-Reply-To: <20260715011438.1274211-1-rosenp@gmail.com>
On 7/15/26 10:14, Rosen Penev wrote:
> Replace the open-coded platform_get_resource() plus devm_ioremap()
> sequence with devm_platform_ioremap_resource(), which fetches the
> resource, requests the region and maps it in one call. Switch the error
> check to IS_ERR()/PTR_ERR() and drop the now-unused struct resource
> pointer.
>
> There is a single IORESOURCE_MEM resource, and the SATA PHY registers
> are mapped separately via of_iomap() from distinct DT nodes, so the
> region reservation added by devm_ioremap_resource() is exclusive and
> does not introduce overlap failures.
>
> The mem-based ata_port_desc() line is dropped along with the resource
> pointer; the remaining per-port description is retained.
>
> Built for ARM (drivers/ata/sata_highbank.o) with LLVM=1.
>
> Assisted-by: opencode:hy3-free
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
Applied to for-7.3. Thanks!
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2026-07-18 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 1:14 [PATCH] ata: sata_highbank: use devm_platform_ioremap_resource Rosen Penev
2026-07-18 3:06 ` Damien Le Moal [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=314972c4-8f66-46d3-bc09-1e05db700688@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=justinstitt@google.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=rosenp@gmail.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