From: Markus Elfring <Markus.Elfring@web.de>
To: "Chin-Ting Kuo" <chin-ting_kuo@aspeedtech.com>,
linux-spi@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, openbmc@lists.ozlabs.org,
"Cédric Le Goater" <clg@redhat.com>,
"Paul Menzel" <pmenzel@molgen.mpg.de>
Cc: lkp@intel.com, LKML <linux-kernel@vger.kernel.org>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Joel Stanley <joel@jms.id.au>, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] spi: aspeed: Use devm_iounmap() to unmap devm_ioremap() memory
Date: Wed, 5 Nov 2025 18:44:27 +0100 [thread overview]
Message-ID: <1a234e96-b41e-4f6c-b23c-e57426ff6aa1@web.de> (raw)
In-Reply-To: <20251105084952.1063489-1-chin-ting_kuo@aspeedtech.com>
> The AHB IO memory for each chip select is mapped using
> devm_ioremap(), so it should be unmapped using devm_iounmap()
> to ensure proper device-managed resource cleanup.
…
* You may occasionally put more than 61 characters into text lines
of such a change description.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc4#n658
* Would another imperative wording become helpful for an improved change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.18-rc4#n94
Regards,
Markus
next prev parent reply other threads:[~2025-11-05 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 8:49 [PATCH] spi: aspeed: Use devm_iounmap() to unmap devm_ioremap() memory Chin-Ting Kuo
2025-11-05 8:52 ` Cédric Le Goater
2025-11-05 14:35 ` Paul Menzel
2025-11-05 17:44 ` Markus Elfring [this message]
2025-11-06 2:53 ` Chin-Ting Kuo
2025-11-06 7:02 ` Markus Elfring
2025-11-06 8:02 ` Chin-Ting Kuo
2025-11-06 11:34 ` Mark Brown
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=1a234e96-b41e-4f6c-b23c-e57426ff6aa1@web.de \
--to=markus.elfring@web.de \
--cc=andrew@codeconstruct.com.au \
--cc=broonie@kernel.org \
--cc=chin-ting_kuo@aspeedtech.com \
--cc=clg@redhat.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=pmenzel@molgen.mpg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox