U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 4/4] configs: ti_omap5_common: Add NAND environment settings
Date: Wed, 27 Feb 2019 13:55:59 -0500	[thread overview]
Message-ID: <20190227185559.GF12046@bill-the-cat> (raw)
In-Reply-To: <20190227075938.7180-5-faiz_abbas@ti.com>

On Wed, Feb 27, 2019 at 01:29:38PM +0530, Faiz Abbas wrote:

> Now that NAND is supported on DRA71x include various NAND environment
> settings
> 
> Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>

Reviewed-by: Tom Rini <trini@konsulko.com>

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190227/cec3245c/attachment.sig>

  reply	other threads:[~2019-02-27 18:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27  7:59 [U-Boot] [PATCH v2 0/4] Add Support for NAND in dra71x-evm Faiz Abbas
2019-02-27  7:59 ` [U-Boot] [PATCH v2 1/4] board: ti: dra71: Add pinmux settings for NAND on DRA71x EVM Faiz Abbas
2019-04-12 16:30   ` [U-Boot] [U-Boot, v2, " Tom Rini
2019-02-27  7:59 ` [U-Boot] [PATCH v2 2/4] arm: dra7: Allow NAND to be enabled " Faiz Abbas
2019-04-12 16:30   ` [U-Boot] [U-Boot, v2, " Tom Rini
2019-02-27  7:59 ` [U-Boot] [PATCH v2 3/4] configs: dra71x-evm: Add Support for NAND Faiz Abbas
2019-04-12 16:30   ` [U-Boot] [U-Boot, v2, " Tom Rini
2019-02-27  7:59 ` [U-Boot] [PATCH v2 4/4] configs: ti_omap5_common: Add NAND environment settings Faiz Abbas
2019-02-27 18:55   ` Tom Rini [this message]
2019-04-12 16:30   ` [U-Boot] [U-Boot, v2, " Tom Rini
2019-03-13 15:05 ` [U-Boot] [PATCH v2 0/4] Add Support for NAND in dra71x-evm Faiz Abbas
2019-03-13 16:01   ` 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=20190227185559.GF12046@bill-the-cat \
    --to=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