From: Frank Rowand <frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Julia Lawall <julia.lawall-L2FTfq7BK8M@public.gmane.org>,
mporter-OWPKS81ov/FWk0Htik3J/w@public.gmane.org,
behanw-k/hB3zQhLwledRVtV/plodBPR1lH4CV8@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org,
pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Grant Likely <glikely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Subject: Re: device tree verification tools
Date: Fri, 4 Nov 2016 13:03:14 -0700 [thread overview]
Message-ID: <581CE982.60605@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1607262241240.3426@hadrien>
On 07/26/16 13:43, Julia Lawall wrote:
> I saw that there will be a microconference on device trees at Linux
> Plumbers. Unfortunately, I won't be able to attend, due to another event
> at the same time, but I was wondering what is the status of verification
> tools for device tree specifications?
>
> thanks,
> julia
>
Hi Julia,
Grant Likely is breathing new life into the verification effort.
-Frank
next prev parent reply other threads:[~2016-11-04 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 20:43 device tree verification tools Julia Lawall
2016-08-03 19:49 ` Frank Rowand
2016-08-03 23:42 ` Stewart Smith
[not found] ` <87vazh8ln8.fsf-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-08-04 5:18 ` Julia Lawall
2016-08-09 3:34 ` Stewart Smith
2016-08-09 3:34 ` Stewart Smith
2016-11-04 20:03 ` Frank Rowand [this message]
[not found] ` <581CE982.60605-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-11-04 20:07 ` Grant Likely
[not found] ` <CACxGe6vFmHRtE+=rJnsWrm7BGqqXBXq8FJq_T0r5deGP5pnCYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-11-04 21:08 ` Julia Lawall
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=581CE982.60605@gmail.com \
--to=frowand.list-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=behanw-k/hB3zQhLwledRVtV/plodBPR1lH4CV8@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=glikely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=julia.lawall-L2FTfq7BK8M@public.gmane.org \
--cc=mporter-OWPKS81ov/FWk0Htik3J/w@public.gmane.org \
--cc=pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.