From: Philipp Zabel <p.zabel@pengutronix.de>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-kernel@vger.kernel.org
Cc: Mark Brown <broonie@kernel.org>,
Drew Fustini <fustini@kernel.org>, Guo Ren <guoren@kernel.org>,
Fu Wei <wefu@redhat.com>,
linux-arm-msm@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH 16/21] reset: remove unneeded 'fast_io' parameter in regmap_config
Date: Thu, 14 Aug 2025 12:56:21 +0200 [thread overview]
Message-ID: <01e5b62d71ef7825a7a61f1785fb2bcb47a92cda.camel@pengutronix.de> (raw)
In-Reply-To: <20250813161517.4746-17-wsa+renesas@sang-engineering.com>
On Mi, 2025-08-13 at 18:15 +0200, Wolfram Sang wrote:
> When using MMIO with regmap, fast_io is implied. No need to set it
> again.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
> No dependencies, can be applied directly to the subsystem tree. Buildbot is
> happy, too.
Applied patch 16 to reset/next, thanks!
[16/21] reset: remove unneeded 'fast_io' parameter in regmap_config
https://git.pengutronix.de/cgit/pza/linux/commit/?id=1527cd3b89f0
regards
Philipp
next prev parent reply other threads:[~2025-08-14 10:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 16:14 [PATCH 00/21] treewide: remove unneeded 'fast_io' parameter in regmap_config Wolfram Sang
2025-08-13 16:14 ` [PATCH 02/21] clk: " Wolfram Sang
2025-08-21 21:46 ` Brian Masney
2025-08-22 5:59 ` Wolfram Sang
2025-08-13 16:14 ` [PATCH 07/21] mailbox: " Wolfram Sang
2025-08-13 16:15 ` [PATCH 15/21] regulator: " Wolfram Sang
2025-08-13 16:15 ` [PATCH 16/21] reset: " Wolfram Sang
2025-08-13 18:28 ` Drew Fustini
2025-08-14 10:56 ` Philipp Zabel [this message]
2025-08-13 16:15 ` [PATCH 18/21] soc: " Wolfram Sang
2025-08-14 9:29 ` Konrad Dybcio
2025-08-13 21:28 ` (subset) [PATCH 00/21] treewide: " Mark Brown
2025-08-14 11:13 ` Mark Brown
2025-08-14 14:18 ` Mark Brown
2025-08-15 14:42 ` Bjorn Andersson
2025-08-20 17:02 ` Vinod Koul
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=01e5b62d71ef7825a7a61f1785fb2bcb47a92cda.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=broonie@kernel.org \
--cc=fustini@kernel.org \
--cc=guoren@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=wefu@redhat.com \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).