From: Andre Przywara <osp-s5aTT1PPrfyzQB+pC5nmwQ@public.gmane.org>
To: David Gibson
<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>,
Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
Cc: devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v2 0/2] dtc: simplify command line invocation
Date: Wed, 1 Jul 2015 00:31:26 +0100 [thread overview]
Message-ID: <1435707088-12800-1-git-send-email-osp@andrep.de> (raw)
Hi,
as promised the revised version of my mini-series.
Compared to the first drop I do not bother anymore to do file name
based guessing in case of an error opening or accessing the input
file. Also the .dts heuristic (first character is a '/') is now gone.
I omitted the third patch ("allow a second parameter to be the output
file name") entirely.
Hope that fits better, if not, let me know!
Cheers,
Andre.
-------------
Most of time I find myself converting .dts to .dtb files and vice
versa, but having to explicitly specify -I and -O every time seems to
be unnecessary. The file names usually have proper extensions, also
a DTB file is easily recognized by its magic.
This series aims to make life easier, by trying to auto-detect the
file types if no explicit -I or -O parameters have been given.
The behaviour with explicit file types specified via these parameters
is not changed.
For details see the respective commit messages.
Andre Przywara (2):
guess input file format based on file content or file name
guess output file format
dtc.c | 62 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 60 insertions(+), 2 deletions(-)
--
1.8.4
next reply other threads:[~2015-06-30 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 23:31 Andre Przywara [this message]
[not found] ` <1435707088-12800-1-git-send-email-osp-s5aTT1PPrfyzQB+pC5nmwQ@public.gmane.org>
2015-06-30 23:31 ` [PATCH v2 1/2] guess input file format based on file content or file name Andre Przywara
2015-06-30 23:31 ` [PATCH v2 2/2] guess output file format Andre Przywara
2015-07-01 3:35 ` [PATCH v2 0/2] dtc: simplify command line invocation 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=1435707088-12800-1-git-send-email-osp@andrep.de \
--to=osp-s5att1pprfyzqb+pc5nmwq@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jdl-CYoMK+44s/E@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).