All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sobota, Justin" <jsobota-l0cyMroinI0@public.gmane.org>
To: "jdl-CYoMK+44s/E@public.gmane.org" <jdl-CYoMK+44s/E@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
	<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: New DTC Release
Date: Wed, 23 Jan 2013 21:57:59 +0000	[thread overview]
Message-ID: <311ECDE3E284F649854AED0B108A0CE114B7939C@DFLE08.ent.ti.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 733 bytes --]

Jon,

Will it be possible to do a new DTC release sometime in the near future?  I've integrated libfdt from DTCv1.3.0 into a TI software component that will be released with a BSD-type license.  During the integration I noticed a lot of applicable fixes have been made on the master since the last release in 2011.  David informed me the master is generally stable enough to consume but I'd feel more comfortable using an official DTC release.

One additional item I brought up with David is the lack of license header in fdt.h and libfdt_env.h.  He responded the lack of license in both headers is an oversight.  If a new release can be spun I'd like to request the license header be added to these files.

Thanks,
Justin


[-- Attachment #1.2: Type: text/html, Size: 2658 bytes --]

[-- Attachment #2: Type: text/plain, Size: 192 bytes --]

_______________________________________________
devicetree-discuss mailing list
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
https://lists.ozlabs.org/listinfo/devicetree-discuss

             reply	other threads:[~2013-01-23 21:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 21:57 Sobota, Justin [this message]
     [not found] ` <311ECDE3E284F649854AED0B108A0CE114B7939C-CXzTdvP5/9qIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2013-01-24 16:47   ` New DTC Release Jon Loeliger

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=311ECDE3E284F649854AED0B108A0CE114B7939C@DFLE08.ent.ti.com \
    --to=jsobota-l0cymroini0@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@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 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.