From: patchwork-bot+linux-soc@kernel.org
To: Alexandre TORGUE <alexandre.torgue@foss.st.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] STM32 Bus firewall for v6.10
Date: Mon, 29 Apr 2024 21:00:46 +0000 [thread overview]
Message-ID: <171442444688.17402.489374273539696029.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <7dc64226-5429-4ab7-a8c8-6053b12e3cf5@foss.st.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Thu, 25 Apr 2024 14:59:16 +0200 you wrote:
> Hi Arnd,
>
> Please consider the first round of STM32 firewall bus patch-set. DT part
> for all MPU SoC will come with teh STM32 DT pull request.
>
> Note that conflict merge have been seen on linux-next for this patch:
> "of: property: fw_devlink: Add support for "access-controller"
>
> [...]
Here is the summary with links:
- [GIT,PULL] STM32 Bus firewall for v6.10
https://git.kernel.org/soc/soc/c/46671fd3e311
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-04-29 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 12:59 [GIT PULL] STM32 Bus firewall for v6.10 Alexandre TORGUE
2024-04-29 21:00 ` patchwork-bot+linux-soc [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=171442444688.17402.489374273539696029.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=soc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).