From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Maxime Ripard
<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/4] libfdt: A few overlay fixes
Date: Fri, 7 Oct 2016 15:08:35 +1100 [thread overview]
Message-ID: <20161007040835.GA29155@umbus.fritz.box> (raw)
In-Reply-To: <20161006113959.30865-1-maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1590 bytes --]
On Thu, Oct 06, 2016 at 01:39:55PM +0200, Maxime Ripard wrote:
> Hi David,
>
> Here are a few patches to fix the things you requested and a few bugs
> encountered while doing so.
>
> Let me know what you think,
All applied, thanks.
Couple of other little errors to correct if you have time:
- BADOVERLAY is listed twice in the error string table (a hangover
from when there was both BADFIXUP and BADOVERLAY, I guess)
- The testcases re-use the same file name for the intermediate
dtbs. That's not a terrible problem, but it can make sorting out
what's going on when there are multiple errors in a test run
harder
- Generated dtb/dts files during the test should generally have a
.test.dtb / .test.dts extension (makes gitignores and clean targets
easier)
- In order for the apply_overlay function to be usable from the
libfdt shared library, you'll need to add it to version.lds
> Maxime
>
> Maxime Ripard (4):
> libfdt: Add BADPHANDLE error string
> libfdt: overlay: Report a bad overlay for mismatching local fixups
> libfdt: overlay: Fix symbols and fixups nodes condition
> tests: overlay: Move back the bad fixup tests
>
> libfdt/fdt_overlay.c | 9 +++++----
> libfdt/fdt_strerror.c | 1 +
> tests/run_tests.sh | 14 +++++++-------
> 3 files changed, 13 insertions(+), 11 deletions(-)
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-10-07 4:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 11:39 [PATCH 0/4] libfdt: A few overlay fixes Maxime Ripard
[not found] ` <20161006113959.30865-1-maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2016-10-06 11:39 ` [PATCH 1/4] libfdt: Add BADPHANDLE error string Maxime Ripard
2016-10-06 11:39 ` [PATCH 2/4] libfdt: overlay: Report a bad overlay for mismatching local fixups Maxime Ripard
2016-10-06 11:39 ` [PATCH 3/4] libfdt: overlay: Fix symbols and fixups nodes condition Maxime Ripard
2016-10-06 11:39 ` [PATCH 4/4] tests: overlay: Move back the bad fixup tests Maxime Ripard
2016-10-07 4:08 ` David Gibson [this message]
[not found] ` <20161007040835.GA29155-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2016-10-10 10:08 ` [PATCH 0/4] libfdt: A few overlay fixes Maxime Ripard
2016-10-10 13:40 ` David Gibson
[not found] ` <20161010134035.GK22498-K0bRW+63XPQe6aEkudXLsA@public.gmane.org>
2016-10-11 7:25 ` Maxime Ripard
2016-10-11 8:16 ` Maxime Ripard
2016-10-11 10:18 ` David Gibson
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=20161007040835.GA29155@umbus.fritz.box \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).