public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Patrice CHOTARD <patrice.chotard@foss.st.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Cc: christophe.kerello@foss.st.com, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v11 0/3] Add STM32MP25 SPI NOR support
Date: Mon, 5 May 2025 14:51:19 +0200	[thread overview]
Message-ID: <a53149e6-2273-458f-9fa3-89fec112f4d4@linaro.org> (raw)
In-Reply-To: <6d697e1e-84da-4988-8564-91430e820fef@foss.st.com>

On 05/05/2025 14:15, Patrice CHOTARD wrote:
> 
> 
> On 5/4/25 18:16, Krzysztof Kozlowski wrote:
>> On 04/05/2025 15:50, Krzysztof Kozlowski wrote:
>>>
>>> On Mon, 28 Apr 2025 10:58:29 +0200, Patrice Chotard wrote:
>>>> This series adds SPI NOR support for STM32MP25 SoCs from STMicroelectronics.
>>>>
>>>> On STM32MP25 SoCs family, an Octo Memory Manager block manages the muxing,
>>>> the memory area split, the chip select override and the time constraint
>>>> between its 2 Octo SPI children.
>>>>
>>>> Due to these depedencies, this series adds support for:
>>>>   - Octo Memory Manager driver.
>>>>   - Octo SPI driver.
>>>>   - yaml schema for Octo Memory Manager and Octo SPI drivers.
>>>>
>>>> [...]
>>>
>>> Applied, thanks!
>>>
>>> [1/3] dt-bindings: memory-controllers: Add STM32 Octo Memory Manager controller
>>>       https://git.kernel.org/krzk/linux-mem-ctrl/c/43eb1b288072641b7de8f5d5c15bde69e6e8589a
>>
>> And dropped everything - it is full of warnings.
> 
> Hi Krzysztof,
> 
> What are the warnings you encountered ?
> 
> On my side, i double check and found nothing wrong neither on bindings side nor on source code side:
> 
> I previously checked that everything was up to date : 

stm32_firewall_device.h:117:5: error: no previous prototype for
‘stm32_firewall_get_firewall’ [-Werror=missing-prototypes]
  117 | int stm32_firewall_get_firewall(struct device_node *np, struct
stm32_firewall *firewall,

and several other like that.

See:
https://krzk.eu/#/builders/38/builds/915
https://krzk.eu/#/builders/40/builds/900


Best regards,
Krzysztof

  reply	other threads:[~2025-05-05 12:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-28  8:58 [PATCH v11 0/3] Add STM32MP25 SPI NOR support Patrice Chotard
2025-04-28  8:58 ` [PATCH v11 1/3] dt-bindings: memory-controllers: Add STM32 Octo Memory Manager controller Patrice Chotard
2025-04-28  8:58 ` [PATCH v11 2/3] memory: Add STM32 Octo Memory Manager driver Patrice Chotard
2025-05-09  8:32   ` Dan Carpenter
2025-05-13  7:54     ` Krzysztof Kozlowski
2025-05-13 15:22       ` Patrice CHOTARD
2025-04-28  8:58 ` [PATCH v11 3/3] MAINTAINERS: add entry for STM32 OCTO MEMORY MANAGER driver Patrice Chotard
2025-05-04 13:50 ` [PATCH v11 0/3] Add STM32MP25 SPI NOR support Krzysztof Kozlowski
2025-05-04 16:16   ` Krzysztof Kozlowski
2025-05-05 12:15     ` Patrice CHOTARD
2025-05-05 12:51       ` Krzysztof Kozlowski [this message]
2025-05-07  9:40 ` 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=a53149e6-2273-458f-9fa3-89fec112f4d4@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=catalin.marinas@arm.com \
    --cc=christophe.kerello@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.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=p.zabel@pengutronix.de \
    --cc=patrice.chotard@foss.st.com \
    --cc=robh@kernel.org \
    --cc=will@kernel.org \
    /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