devicetree-compiler.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org,
	jdl-CYoMK+44s/E@public.gmane.org,
	devicetree-compiler-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC PATCH v5 1/2] dtc: dts source location annotation
Date: Wed, 30 Sep 2015 20:36:54 -0700	[thread overview]
Message-ID: <560CAA56.3050402@gmail.com> (raw)
In-Reply-To: <560CA9FB.6050700-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 9/30/2015 8:35 PM, Frank Rowand wrote:
> From: Frank Rowand <frank.rowand-/MT0OVThwyLZJqsBc5GL+g@public.gmane.org>
> 
> Proof of concept patch.
> 
> Annotates input source file and line number of nodes and properties
> as comments in output .dts file when --annotate flag is supplied.

< snip >

Sorry, bad subject.  Patch 2/2, not 1/2.

-Frank

  parent reply	other threads:[~2015-10-01  3:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01  3:29 [RFC PATCH v5 0/2] dtc: dts source location annotation Frank Rowand
     [not found] ` <560CA87E.1010103-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-10-01  3:32   ` [RFC PATCH v5 1/2] dtc: protect against null pointer dereference in srcpos_string() Frank Rowand
     [not found]     ` <560CA95C.6010109-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-10-01  5:32       ` David Gibson
2015-10-01  3:35   ` [RFC PATCH v5 1/2] dtc: dts source location annotation Frank Rowand
     [not found]     ` <560CA9FB.6050700-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-10-01  3:36       ` Frank Rowand [this message]
2015-10-01  5:49       ` David Gibson
2015-10-03  4:24         ` Frank Rowand
     [not found]           ` <560F586F.8040302-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-10-03  4:29             ` Frank Rowand

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=560CAA56.3050402@gmail.com \
    --to=frowand.list-re5jqeeqqe8avxtiumwx3w@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).