From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Jack Miller <jack-jZyo8ZIaZD9AfugRpC6u6w@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Properly handle embedded nul delimited string lists
Date: Fri, 8 Aug 2014 19:18:32 +1000 [thread overview]
Message-ID: <20140808091832.GF10949@voom.redhat.com> (raw)
In-Reply-To: <1407358323-14044-2-git-send-email-jack-jZyo8ZIaZD9AfugRpC6u6w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
On Wed, Aug 06, 2014 at 03:52:03PM -0500, Jack Miller wrote:
> For example:
>
> reserved-names="res1\0res2\0res3";
>
> Where \0 is an actual embedded NUL in the source instead of a string
> escape. To achieve this, use the len given by the lexer instead of
> strlen.
>
> Without this patch dtc will mangle the output and possibly hang on
> realloc.
Looks good to me. Applied, thanks.
--
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: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-08 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 20:52 Embedded NUL (again) Jack Miller
[not found] ` <1407358323-14044-1-git-send-email-jack-jZyo8ZIaZD9AfugRpC6u6w@public.gmane.org>
2014-08-06 20:52 ` [PATCH] Properly handle embedded nul delimited string lists Jack Miller
[not found] ` <1407358323-14044-2-git-send-email-jack-jZyo8ZIaZD9AfugRpC6u6w@public.gmane.org>
2014-08-08 9:18 ` David Gibson [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-06 19:31 Embedded NUL (again) Jack Miller
[not found] ` <1407353512-12182-1-git-send-email-jack-jZyo8ZIaZD9AfugRpC6u6w@public.gmane.org>
2014-08-06 19:31 ` [PATCH] Properly handle embedded nul delimited string lists Jack Miller
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=20140808091832.GF10949@voom.redhat.com \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jack-jZyo8ZIaZD9AfugRpC6u6w@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).