From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: "Clément Le Goffic" <legoffic.clement@gmail.com>,
"Gatien Chevallier" <gatien.chevallier@foss.st.com>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.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: Thu, 8 Jan 2026 16:24:24 +0100 [thread overview]
Message-ID: <95a72b44-3802-422e-a720-6e9578769cce@foss.st.com> (raw)
In-Reply-To: <20250916-b4-firewall-upstream-v7-1-6038cf1e61d8@gmail.com>
Hi Clément
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(-)
>
...
Sorry this patch is a bit old. Can you rebase it please ?
Then I'll merge it.
Thanks in advance.
Alex
prev parent reply other threads:[~2026-01-08 15:24 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
2026-01-08 15:24 ` Alexandre TORGUE [this message]
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=95a72b44-3802-422e-a720-6e9578769cce@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=clement.legoffic@foss.st.com \
--cc=gatien.chevallier@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®