Re: [PATCH v8] bus: firewall: move stm32_firewall header file in include folder

[Alexandre TORGUE]

Dear Clément

On 2/10/26 20:05, Clément Le Goffic wrote:
> From: Clément Le Goffic <clement.legoffic@xxxxxxxxxxx>
>
> Other driver than RIFSC and ETZPC can implement firewall ops, such as
> RCC.
> In order for them to have access to the ops and type of this framework,
> we need to get the `stm32_firewall.h` file in the include/ folder.
>
> Signed-off-by: Clément Le Goffic <clement.legoffic@xxxxxxxxxxx>
> Acked-by: Gatien Chevallier <gatien.chevallier@xxxxxxxxxxx>
> Signed-off-by: Clément Le Goffic <legoffic.clement@xxxxxxxxx>
> ---
> Changes in v8:
> - Rebase on v6.19.0
> - Use uppercase for peripheral name in commit message.
> - Link to v7: https://lore.kernel.org/r/20250916-b4-firewall-upstream-v7-1-6038cf1e61d8@xxxxxxxxx
>
> The v7 is a subset of the v6 and other prior versions, splited to simplify
> the review and merging process.
>
> Changes in v7:
> - None
> - Link to v6: https://lore.kernel.org/all/20250909-b4-ddrperfm-upstream-v6-1-ce082cc801b5@xxxxxxxxx/
> ---
>   drivers/bus/stm32_etzpc.c                       | 3 +--
>   drivers/bus/stm32_firewall.c                    | 3 +--
>   drivers/bus/stm32_rifsc.c                       | 3 +--
>   {drivers => include/linux}/bus/stm32_firewall.h | 0
>   4 files changed, 3 insertions(+), 6 deletions(-)

Applied on stm32-next.

Regards
Alex