From: Krzysztof Kozlowski <krzk@kernel.org>
To: Patrice CHOTARD <patrice.chotard@foss.st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Christophe Kerello <christophe.kerello@foss.st.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] memory: stm32_omm: Fix req2ack update test
Date: Mon, 11 Aug 2025 14:53:43 +0200 [thread overview]
Message-ID: <55582d2a-5357-457a-b121-ce6be25d6ae3@kernel.org> (raw)
In-Reply-To: <a55774bf-1133-48c2-ad20-7a69f340bd78@foss.st.com>
On 11/08/2025 14:49, Patrice CHOTARD wrote:
>
>
> On 8/11/25 09:09, Krzysztof Kozlowski wrote:
>> On 07/08/2025 09:34, Patrice Chotard wrote:
>>> If "st,omm-req2ack-ns" property is found and its value is not 0,
>>> the current test doesn't allow to compute and set req2ack value,
>>> Fix this test.
>>>
>>> Fixes: 8181d061dcff ("memory: Add STM32 Octo Memory Manager driver")
>>> Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
>>> ---
>>> Changes in v2:
>>> - Add more detail in commit message
>>> - Remove "Cc: <stable@vger.kernel.org>" tag as the fixed patch is not part of a LTS.
>>
>> Why LTS would matter? Which kernel is being fixed here?
>
> Hi Krzysztof,
>
> The fixed kernel is v6.16.
Then you need Cc stable. Only unreleased kernels are... well, unreleased.
Fixed while applying, but your other patches might have same issue.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-11 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 7:34 [PATCH v2] memory: stm32_omm: Fix req2ack update test Patrice Chotard
2025-08-11 7:09 ` Krzysztof Kozlowski
2025-08-11 12:49 ` Patrice CHOTARD
2025-08-11 12:53 ` Krzysztof Kozlowski [this message]
2025-08-11 12:54 ` Krzysztof Kozlowski
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=55582d2a-5357-457a-b121-ce6be25d6ae3@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=christophe.kerello@foss.st.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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