From: Eugeniu Rosca <erosca@de.adit-jv.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/5] fdt: boot_get_fdt: really boot w/o FDT when "goto no_fdt"
Date: Thu, 25 Apr 2019 19:04:32 +0200 [thread overview]
Message-ID: <20190425170432.GB15318@vmlxhi-102.adit-jv.com> (raw)
In-Reply-To: <CAPnjgZ0W63NUMedx0+5drPGwbpQq4dKm=6v91DEOKFndZ2mccw@mail.gmail.com>
Hi Simon,
On Sun, Apr 21, 2019 at 07:38:52PM -0700, sjg at google.com wrote:
[..]
> Can we create a test of the boot_get_fdt() behaviour?
>
> We have test_fit and test_vboot as possible examples, although perhaps
> a test that directly calls this function would be better?
On my list. Thanks.
>
> Regards,
> Simon
>
>
>
> Applied to u-boot-dm, thanks!
--
Best Regards,
Eugeniu.
next prev parent reply other threads:[~2019-04-25 17:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 10:45 [U-Boot] [PATCH v2 0/5] boot_get_fdt: clean up and use 'fdtaddr' as fallback for Android Eugeniu Rosca
2019-04-01 10:45 ` [U-Boot] [PATCH v2 1/5] fdt: boot_get_fdt: remove redundant zeroing out Eugeniu Rosca
2019-04-18 4:33 ` Simon Glass
2019-04-18 10:18 ` Eugeniu Rosca
2019-04-20 1:36 ` Simon Glass
2019-04-22 2:38 ` sjg at google.com
2019-04-25 17:00 ` Eugeniu Rosca
2019-04-01 10:45 ` [U-Boot] [PATCH v2 2/5] fdt: boot_get_fdt: really boot w/o FDT when "goto no_fdt" Eugeniu Rosca
2019-04-21 19:26 ` Simon Glass
2019-04-22 2:38 ` sjg at google.com
2019-04-25 17:04 ` Eugeniu Rosca [this message]
2019-04-01 10:45 ` [U-Boot] [PATCH v2 3/5] fdt: boot_get_fdt: simplify no_fdt handling (non-functional) Eugeniu Rosca
2019-04-21 19:26 ` Simon Glass
2019-04-22 2:38 ` sjg at google.com
2019-04-01 10:45 ` [U-Boot] [PATCH v2 4/5] fdt: boot_get_fdt: android: compress " Eugeniu Rosca
2019-04-21 19:26 ` Simon Glass
2019-04-22 2:38 ` sjg at google.com
2019-04-01 10:52 ` [U-Boot] [PATCH v2 5/5] fdt: boot_get_fdt: android: use ENV 'fdtaddr' as fallback Eugeniu Rosca
2019-04-01 15:26 ` Eugeniu Rosca
2019-04-21 19:26 ` Simon Glass
2019-04-22 2:38 ` sjg at google.com
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=20190425170432.GB15318@vmlxhi-102.adit-jv.com \
--to=erosca@de.adit-jv.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 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.