From: Gatien CHEVALLIER <gatien.chevallier@foss.st.com>
To: "Clément Le Goffic" <legoffic.clement@gmail.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>
Cc: linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Clément Le Goffic" <clement.legoffic@foss.st.com>
Subject: Re: [PATCH v7] bus: firewall: move stm32_firewall header file in include folder
Date: Mon, 22 Sep 2025 09:52:39 +0200 [thread overview]
Message-ID: <d7a4e6c6-6670-41e3-9537-4be705ca3805@foss.st.com> (raw)
In-Reply-To: <20250916-b4-firewall-upstream-v7-1-6038cf1e61d8@gmail.com>
On 9/16/25 11:07, Clément Le Goffic wrote:
> From: Clément Le Goffic <clement.legoffic@foss.st.com>
>
> 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@foss.st.com>
> Signed-off-by: Clément Le Goffic <legoffic.clement@gmail.com>
> ---
> This 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@gmail.com/
> ---
> 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(-)
>
> diff --git a/drivers/bus/stm32_etzpc.c b/drivers/bus/stm32_etzpc.c
> index 7fc0f16960be..4918a14e507e 100644
> --- a/drivers/bus/stm32_etzpc.c
> +++ b/drivers/bus/stm32_etzpc.c
> @@ -5,6 +5,7 @@
>
> #include <linux/bitfield.h>
> #include <linux/bits.h>
> +#include <linux/bus/stm32_firewall.h>
> #include <linux/device.h>
> #include <linux/err.h>
> #include <linux/init.h>
> @@ -16,8 +17,6 @@
> #include <linux/platform_device.h>
> #include <linux/types.h>
>
> -#include "stm32_firewall.h"
> -
> /*
> * ETZPC registers
> */
> diff --git a/drivers/bus/stm32_firewall.c b/drivers/bus/stm32_firewall.c
> index 2fc9761dadec..ef4988054b44 100644
> --- a/drivers/bus/stm32_firewall.c
> +++ b/drivers/bus/stm32_firewall.c
> @@ -5,6 +5,7 @@
>
> #include <linux/bitfield.h>
> #include <linux/bits.h>
> +#include <linux/bus/stm32_firewall.h>
> #include <linux/bus/stm32_firewall_device.h>
> #include <linux/device.h>
> #include <linux/err.h>
> @@ -18,8 +19,6 @@
> #include <linux/types.h>
> #include <linux/slab.h>
>
> -#include "stm32_firewall.h"
> -
> /* Corresponds to STM32_FIREWALL_MAX_EXTRA_ARGS + firewall ID */
> #define STM32_FIREWALL_MAX_ARGS (STM32_FIREWALL_MAX_EXTRA_ARGS + 1)
>
> diff --git a/drivers/bus/stm32_rifsc.c b/drivers/bus/stm32_rifsc.c
> index 4cf1b60014b7..643ddd0a5f54 100644
> --- a/drivers/bus/stm32_rifsc.c
> +++ b/drivers/bus/stm32_rifsc.c
> @@ -5,6 +5,7 @@
>
> #include <linux/bitfield.h>
> #include <linux/bits.h>
> +#include <linux/bus/stm32_firewall.h>
> #include <linux/device.h>
> #include <linux/err.h>
> #include <linux/init.h>
> @@ -16,8 +17,6 @@
> #include <linux/platform_device.h>
> #include <linux/types.h>
>
> -#include "stm32_firewall.h"
> -
> /*
> * RIFSC offset register
> */
> diff --git a/drivers/bus/stm32_firewall.h b/include/linux/bus/stm32_firewall.h
> similarity index 100%
> rename from drivers/bus/stm32_firewall.h
> rename to include/linux/bus/stm32_firewall.h
>
> ---
> base-commit: 46a51f4f5edade43ba66b3c151f0e25ec8b69cb6
> change-id: 20250916-b4-firewall-upstream-dfe8588a21f8
>
> Best regards,
> --
> Clément Le Goffic <legoffic.clement@gmail.com>
>
Hi Clément,
Acked-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
Nit: peripheral names should be uppercase in the commit message.
Thanks,
Gatien
next prev parent reply other threads:[~2025-09-22 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 9:07 Clément Le Goffic
2025-09-22 7:52 ` Gatien CHEVALLIER [this message]
2026-01-08 15:24 ` Alexandre TORGUE
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=d7a4e6c6-6670-41e3-9537-4be705ca3805@foss.st.com \
--to=gatien.chevallier@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=clement.legoffic@foss.st.com \
--cc=legoffic.clement@gmail.com \
--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 \
/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
all inboxes | Powered by JetHome®