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: [PATCH v4 1/3] env: split env_import_redund() into 2 functions
Date: Fri, 30 Oct 2020 14:46:28 -0400	[thread overview]
Message-ID: <20201030184628.GX5340@bill-the-cat> (raw)
In-Reply-To: <20201010082806.2260318-2-hs@denx.de>

On Sat, Oct 10, 2020 at 10:28:04AM +0200, Heiko Schocher wrote:

> split from env_import_redund() the part which checks
> which Environment is valid into a separate function
> called env_check_redund() and call it from env_import_redund().
> 
> So env_check_redund() can be used from places which also
> need to do this checks.
> 
> Signed-off-by: Heiko Schocher <hs@denx.de>
> Reviewed-by: Simon Glass <sjg@chromium.org>

Applied to u-boot/master, thanks!

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

  parent reply	other threads:[~2020-10-30 18:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-10  8:28 [PATCH v4 0/3] env: Access Environment in SPI flashes before relocation Heiko Schocher
2020-10-10  8:28 ` [PATCH v4 1/3] env: split env_import_redund() into 2 functions Heiko Schocher
2020-10-12  3:35   ` Simon Glass
2020-10-30 18:46   ` Tom Rini [this message]
2020-10-10  8:28 ` [PATCH v4 2/3] env: Access Environment in SPI flashes before relocation Heiko Schocher
2020-10-12  3:35   ` Simon Glass
2020-10-30 18:46   ` Tom Rini
2020-10-30 23:51   ` Michael Walle
2020-10-31  0:07     ` Tom Rini
2020-10-31  0:25       ` Michael Walle
2020-11-02  5:20       ` Heiko Schocher
2020-10-10  8:28 ` [PATCH v4 3/3] imx6: enable early spi environment access on aristainetos boards Heiko Schocher
2020-10-30 18:46   ` 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=20201030184628.GX5340@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