From: Philipp Zabel <p.zabel@pengutronix.de>
To: Patrice Chotard <patrice.chotard@foss.st.com>,
Mark Brown <broonie@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] reset: Add devm_reset_control_array_get_exclusive_released()
Date: Mon, 05 May 2025 15:28:51 +0200 [thread overview]
Message-ID: <1431aa0cb021da0056b9de594c3332045b770d07.camel@pengutronix.de> (raw)
In-Reply-To: <20250411-b4-upstream_ospi_reset_update-v2-1-4de7f5dd2a91@foss.st.com>
On Fr, 2025-04-11 at 14:41 +0200, Patrice Chotard wrote:
> Add the released variant of devm_reset_control_array_get_exclusive().
> Needed by spi-smt32-ospi driver as same reset line is ulso used by
> stm32-omm driver.
>
> Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
> Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
Applied patch 1 to reset/next, thanks!
[1/2] reset: Add devm_reset_control_array_get_exclusive_released()
https://git.pengutronix.de/cgit/pza/linux/commit/?id=6b3754009f87
regards
Philipp
next prev parent reply other threads:[~2025-05-05 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 12:41 [PATCH v2 0/2] reset: Add devm_reset_control_array_get_exclusive_released() Patrice Chotard
2025-04-11 12:41 ` [PATCH v2 1/2] " Patrice Chotard
2025-05-05 13:28 ` Philipp Zabel [this message]
2025-04-11 12:41 ` [PATCH v2 2/2] spi: stm32-ospi: Make usage of reset_control_acquire/release() API Patrice Chotard
2025-05-05 13:12 ` Philipp Zabel
2025-05-07 16:04 ` Patrice CHOTARD
2025-06-09 19:33 ` [PATCH v2 0/2] reset: Add devm_reset_control_array_get_exclusive_released() 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=1431aa0cb021da0056b9de594c3332045b770d07.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=alexandre.torgue@foss.st.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=patrice.chotard@foss.st.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).