public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: sbabic@denx.de
To: Marek Vasut <marex@denx.de>,u-boot@lists.denx.de
Subject: [PATCH 2/2] thermal: imx_tmu: Move architecture code into driver
Date: Sun, 21 May 2023 19:09:05 +0200 (CEST)	[thread overview]
Message-ID: <20230521170909.E4D00846D8@phobos.denx.de> (raw)
In-Reply-To: <20230404192510.160819-2-marex@denx.de>

> Stop polluting the architecture directory with driver specific code,
> move it into driver where it should be. Split the code slightly so
> the MX8MM/MX8MN fuse readout and programming and MX8MP fuse readout
> and programming are in their separate functions, and called in case
> of matching SoC.
> Signed-off-by: Marek Vasut <marex@denx.de>
> Reviewed-by: Fabio Estevam <festevam@denx.de>
> Reviewed-by: Andrejs Cainikovs <andrejs.cainikovs@toradex.com>
Applied to u-boot-imx, master, thanks !

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,        Managing Director: Erika Unter  
HRB 165235 Munich,   Office: Kirchenstr.5, 82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================

  parent reply	other threads:[~2023-05-21 17:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04 19:25 [PATCH 1/2] thermal: imx_tmu: Clean up all prints Marek Vasut
2023-04-04 19:25 ` [PATCH 2/2] thermal: imx_tmu: Move architecture code into driver Marek Vasut
2023-04-04 21:05   ` Fabio Estevam
2023-04-05  9:01     ` Andrejs Cainikovs
2023-05-21 17:09   ` sbabic [this message]
2023-04-04 21:04 ` [PATCH 1/2] thermal: imx_tmu: Clean up all prints Fabio Estevam
2023-04-05  9:00   ` Andrejs Cainikovs
2023-05-21 16:55 ` sbabic

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=20230521170909.E4D00846D8@phobos.denx.de \
    --to=sbabic@denx.de \
    --cc=marex@denx.de \
    --cc=u-boot@lists.denx.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