devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: Devicetree Compiler
	<devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: David Gibson
	<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>,
	Simon Glass <sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Subject: [PATCH 0/3] Fix some code nits
Date: Sun,  6 Mar 2016 20:12:45 -0700	[thread overview]
Message-ID: <1457320368-27248-1-git-send-email-sjg@chromium.org> (raw)

I notice these when I sync with U-Boot's copy of libfdt.h. I'm not sure if
they are considered incorrect in dtc, but here's a little series anyway.

There are still lots of places that use eight spaces instead of a tab. I've
assumed that is intentional and left it alone.


Simon Glass (3):
  Correct space-after-tab in libfdt.h
  Correct line lengths in libfdt.h
  Correct a missing space in a fdt_header cast

 libfdt/libfdt.h | 60 +++++++++++++++++++++++++++++++++------------------------
 1 file changed, 35 insertions(+), 25 deletions(-)

-- 
2.7.0.rc3.207.g0ac5344

             reply	other threads:[~2016-03-07  3:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07  3:12 Simon Glass [this message]
     [not found] ` <1457320368-27248-1-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2016-03-07  3:12   ` [PATCH 1/3] Correct space-after-tab in libfdt.h Simon Glass
2016-03-07  3:12   ` [PATCH 2/3] Correct line lengths " Simon Glass
2016-03-07  3:12   ` [PATCH 3/3] Correct a missing space in a fdt_header cast Simon Glass
2016-03-07  4:38   ` [PATCH 0/3] Fix some code nits 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=1457320368-27248-1-git-send-email-sjg@chromium.org \
    --to=sjg-f7+t8e8rja9g9huczpvpmw@public.gmane.org \
    --cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@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).