U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Svyatoslav Ryhel <clamor95@gmail.com>, Tom Rini <trini@konsulko.com>
Cc: "Jonas Schwöbel" <jonasschwoebel@yahoo.de>,
	"Thierry Reding" <treding@nvidia.com>,
	"Francesco Dolcini" <francesco.dolcini@toradex.com>,
	"Joe Hershberger" <joe.hershberger@ni.com>,
	"Marcel Ziswiler" <marcel.ziswiler@toradex.com>,
	"Fabio Estevam" <festevam@gmail.com>,
	"Simon Glass" <sjg@chromium.org>,
	"Emanuele Ghidoli" <emanuele.ghidoli@toradex.com>,
	"Martyn Welch" <martyn.welch@collabora.com>,
	u-boot@lists.denx.de
Subject: Re: [PATCH v1 0/1] board: tegra: convert boards to text env
Date: Mon, 5 Aug 2024 07:33:43 +0200	[thread overview]
Message-ID: <20240805053343.GB7516@francesco-nb> (raw)
In-Reply-To: <20240801055738.7601-1-clamor95@gmail.com>

Hello Tom,

On Thu, Aug 01, 2024 at 08:57:37AM +0300, Svyatoslav Ryhel wrote:
> Move env stuff into dedicated files in boards (1st stage).

Is there any plan or expectation to move existing boards to text env file?
And what about newly added boards?

Francesco


  parent reply	other threads:[~2024-08-05  5:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-01  5:57 [PATCH v1 0/1] board: tegra: convert boards to text env Svyatoslav Ryhel
2024-08-01  5:57 ` [PATCH v1 1/1] board: tegra: convert tegra-based " Svyatoslav Ryhel
2024-08-05  5:31   ` Francesco Dolcini
2024-08-05  7:01     ` Svyatoslav Ryhel
2024-08-05  7:05       ` Francesco Dolcini
2024-08-05  7:06         ` Svyatoslav Ryhel
2024-08-05  7:08           ` Francesco Dolcini
2024-08-05  7:10             ` Svyatoslav Ryhel
2024-08-05 15:07             ` Svyatoslav Ryhel
2024-08-05  5:33 ` Francesco Dolcini [this message]
2024-08-05  6:03   ` [PATCH v1 0/1] board: tegra: convert " Svyatoslav Ryhel
2024-08-05  6:12     ` Francesco Dolcini
2024-08-05 18:14   ` Tom Rini

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=20240805053343.GB7516@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=clamor95@gmail.com \
    --cc=emanuele.ghidoli@toradex.com \
    --cc=festevam@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=joe.hershberger@ni.com \
    --cc=jonasschwoebel@yahoo.de \
    --cc=marcel.ziswiler@toradex.com \
    --cc=martyn.welch@collabora.com \
    --cc=sjg@chromium.org \
    --cc=treding@nvidia.com \
    --cc=trini@konsulko.com \
    --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