All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Neha Malcom Francis <n-francis@ti.com>
Cc: u-boot@lists.denx.de, n-jain1@ti.com, u-kumar1@ti.com, vigneshr@ti.com
Subject: Re: [PATCH v2 1/3] include: environment: ti: Use .env for environment variables
Date: Wed, 29 Mar 2023 21:54:09 -0400	[thread overview]
Message-ID: <20230330015409.GL6083@bill-the-cat> (raw)
In-Reply-To: <20230315052745.110502-1-n-francis@ti.com>

[-- Attachment #1: Type: text/plain, Size: 413 bytes --]

On Wed, Mar 15, 2023 at 10:57:43AM +0530, Neha Malcom Francis wrote:

> Add K3 common environment variables to .env. We retain the old-style C
> environment .h files to maintain compatibility with other K3 boards that
> have not moved to using .env yet.
> 
> Signed-off-by: Neha Malcom Francis <n-francis@ti.com>
> Reviewed-by: Tom Rini <trini@konsulko.com>

Applied to u-boot/next, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      parent reply	other threads:[~2023-03-30  1:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-15  5:27 [PATCH v2 1/3] include: environment: ti: Use .env for environment variables Neha Malcom Francis
2023-03-15  5:27 ` [PATCH v2 2/3] include: configs: j721s2_evm: Change to using .env Neha Malcom Francis
2023-03-17  5:57   ` Nikhil M Jain
2023-03-30  1:54   ` Tom Rini
2023-03-15  5:27 ` [PATCH v2 3/3] include: configs: j721e_evm: " Neha Malcom Francis
2023-03-30  1:54   ` Tom Rini
2023-03-16 18:16 ` [PATCH v2 1/3] include: environment: ti: Use .env for environment variables Tom Rini
2023-03-30  1:54 ` Tom Rini [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=20230330015409.GL6083@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=n-francis@ti.com \
    --cc=n-jain1@ti.com \
    --cc=u-boot@lists.denx.de \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.