From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Oleksij Rempel <o.rempel@pengutronix.de>
Cc: David Jander <david@protonic.nl>
Subject: Re: [PATCH v1 1/4] arm: boards: protonic-stm32mp13: Add support for MECT1S board
Date: Mon, 07 Apr 2025 15:35:24 +0200 [thread overview]
Message-ID: <174403292402.3652526.16407921799170562249.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250331123032.626219-1-o.rempel@pengutronix.de>
On Mon, 31 Mar 2025 14:30:29 +0200, Oleksij Rempel wrote:
> Introduce support for the Protonic MECT1S r1 board based on STM32MP133.
>
>
Applied, thanks!
[1/4] arm: boards: protonic-stm32mp13: Add support for MECT1S board
https://git.pengutronix.de/cgit/barebox/commit/?id=535943973d36 (link may not be stable)
[2/4] arm: boards: protonic-stm32mp13: Use unique board driver name
https://git.pengutronix.de/cgit/barebox/commit/?id=3b0a45e63c8d (link may not be stable)
[3/4] arm: boards: protonic-stm32mp: fix stack corruption by passing correct ctx to stm32_bsec_optee_ta_close()
https://git.pengutronix.de/cgit/barebox/commit/?id=765deba962f6 (link may not be stable)
[4/4] arm: boards: protonic-stm32mp: free shift register GPIOs after use
https://git.pengutronix.de/cgit/barebox/commit/?id=06515f69adf4 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-04-07 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 12:30 Oleksij Rempel
2025-03-31 12:30 ` [PATCH v1 2/4] arm: boards: protonic-stm32mp13: Use unique board driver name Oleksij Rempel
2025-03-31 12:30 ` [PATCH v1 3/4] arm: boards: protonic-stm32mp: fix stack corruption by passing correct ctx to stm32_bsec_optee_ta_close() Oleksij Rempel
2025-03-31 12:30 ` [PATCH v1 4/4] arm: boards: protonic-stm32mp: free shift register GPIOs after use Oleksij Rempel
2025-04-07 13:35 ` Sascha Hauer [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=174403292402.3652526.16407921799170562249.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=david@protonic.nl \
--cc=o.rempel@pengutronix.de \
/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