[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ae7b8134-923c-4967-b25c-fc1411fd0602@foss.st.com>
Date: Fri, 16 May 2025 14:56:22 +0200
From: Patrice CHOTARD <patrice.chotard@...s.st.com>
To: Mark Brown <broonie@...nel.org>
CC: Philipp Zabel <p.zabel@...gutronix.de>,
Maxime Coquelin
<mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
<linux-kernel@...r.kernel.org>, <linux-spi@...r.kernel.org>,
<linux-stm32@...md-mailman.stormreply.com>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v5] spi: stm32-ospi: Make usage of
reset_control_acquire/release() API
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
Powered by blists - more mailing lists