From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Mark Brown <broonie@kernel.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<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 v5] spi: stm32-ospi: Make usage of reset_control_acquire/release() API
Date: Fri, 16 May 2025 14:56:22 +0200 [thread overview]
Message-ID: <ae7b8134-923c-4967-b25c-fc1411fd0602@foss.st.com> (raw)
In-Reply-To: <aCWxusdUYgeGRaqk@finisterre.sirena.org.uk>
On 5/15/25 11:19, Mark Brown wrote:
> On Wed, May 14, 2025 at 03:56:01PM +0200, Patrice Chotard wrote:
>
>> This patch is dependent on commit 6b3754009f87
>> ("reset: Add devm_reset_control_array_get_exclusive_released()")
>> available on tag reset-for-v6.16.
>
> When telling people about dependencies like this the standard thing is
> to also specify the repostiory, or link to a pull request. The git
> repository is needed to actually pull the tag. This appears to be the
> PR at:
>
> https://lore.kernel.org/all/20250513092516.3331585-1-p.zabel@pengutronix.de/
>
> which is the full reset pull request for v6.16. The commit you
> referenced isn't the tagged commit, it's further back in the history
> but still has a whole new reset driver backed up behind it. I'd have
> expected that if this was expected to be pulled into other subsystems
> it'd be on a topic branch and directly tagged?
Hi Mark
Sorry for that, how do you want me to proceed ?
Thanks
Patrice
prev parent reply other threads:[~2025-05-16 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 13:56 [PATCH v5] spi: stm32-ospi: Make usage of reset_control_acquire/release() API Patrice Chotard
2025-05-15 9:19 ` Mark Brown
2025-05-16 12:56 ` Patrice CHOTARD [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=ae7b8134-923c-4967-b25c-fc1411fd0602@foss.st.com \
--to=patrice.chotard@foss.st.com \
--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=p.zabel@pengutronix.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;
as well as URLs for NNTP newsgroup(s).