From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 1/5] ARM: i.MX: ele: move ELE_READ_SHADOW_REQ definition
Date: Wed, 13 Mar 2024 08:42:22 +0100 [thread overview]
Message-ID: <171031574225.966191.3470515873612262015.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20240311102152.360762-1-s.hauer@pengutronix.de>
On Mon, 11 Mar 2024 11:21:48 +0100, Sascha Hauer wrote:
> The ELE request defines are in include/mach/imx/ele.h, move definition
> of ELE_READ_SHADOW_REQ there as well.
>
>
Applied, thanks!
[1/5] ARM: i.MX: ele: move ELE_READ_SHADOW_REQ definition
https://git.pengutronix.de/cgit/barebox/commit/?id=2ec5d544549e (link may not be stable)
[2/5] ARM: i.MX: ele: add function comments
https://git.pengutronix.de/cgit/barebox/commit/?id=f95b4906c0f7 (link may not be stable)
[3/5] ARM: i.MX: ele: add ele_write_shadow_fuse
https://git.pengutronix.de/cgit/barebox/commit/?id=2554f8daa381 (link may not be stable)
[4/5] nvmem: add nvmem_device_get_device()
https://git.pengutronix.de/cgit/barebox/commit/?id=50c4a22e1232 (link may not be stable)
[5/5] nvmem: imx-ocotp-ele: implement permanent write support
https://git.pengutronix.de/cgit/barebox/commit/?id=9b799d058e46 (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2024-03-13 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 10:21 Sascha Hauer
2024-03-11 10:21 ` [PATCH 2/5] ARM: i.MX: ele: add function comments Sascha Hauer
2024-03-11 10:21 ` [PATCH 3/5] ARM: i.MX: ele: add ele_write_shadow_fuse Sascha Hauer
2024-03-11 10:21 ` [PATCH 4/5] nvmem: add nvmem_device_get_device() Sascha Hauer
2024-03-11 10:21 ` [PATCH 5/5] nvmem: imx-ocotp-ele: implement permanent write support Sascha Hauer
2024-03-13 7:42 ` 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=171031574225.966191.3470515873612262015.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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