From: Jack Miller <jack-jZyo8ZIaZD9AfugRpC6u6w@public.gmane.org>
To: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] Nul delimiter redux
Date: Tue, 24 Jun 2014 14:50:37 -0500 [thread overview]
Message-ID: <1403639439-1032-1-git-send-email-jack@codezen.org> (raw)
I missent the last patches (TIL telling send-email 'n' will still send the
remaining patches =P). Half way through composing, I realized that I was
probably missing untracked .dtbs thanks to .gitignore.
Anyway, so the first patch uses *.test.dtb suffix, or *test_tree1.dtb suffixes
to delete instead of *.dtb so that an included .dtb won't be eliminated. It
would've been easier to just to suffix the one file I wanted to include, but I
tried to take a hint from the test.dts. The only hack is that the other dtbs
generated by "make tests" are explicitly included in the cleanup list.
This is pretty invasive for a test of a five character patch, but it should
make it easier if binary tests are added later.
Other patch is the same as the previous ones, just merged and with the test.dts
name change.
- Jack
--
To unsubscribe from this list: send the line "unsubscribe devicetree-compiler" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-06-24 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 19:50 Jack Miller [this message]
[not found] ` <1403639439-1032-1-git-send-email-jack-jZyo8ZIaZD9AfugRpC6u6w@public.gmane.org>
2014-06-24 19:50 ` [PATCH 1/2] Selective .dtb deletion on make clean Jack Miller
[not found] ` <1403639439-1032-2-git-send-email-jack-jZyo8ZIaZD9AfugRpC6u6w@public.gmane.org>
2014-07-04 13:33 ` David Gibson
2014-06-24 19:50 ` [PATCH 2/2] Properly handle 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=1403639439-1032-1-git-send-email-jack@codezen.org \
--to=jack-jzyo8ziazd9afugrpc6u6w@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@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).