From: Jon Loeliger <jdl@jdl.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: Outstanding DTC patches?
Date: Fri, 04 Jan 2008 08:38:21 -0600 [thread overview]
Message-ID: <E1JAngj-0003ih-Or@jdl.com> (raw)
In-Reply-To: Your message of "Fri, 04 Jan 2008 13:43:24 +1100." <20080104024324.GA4326@localhost.localdomain>
So, like, the other day David Gibson mumbled:
> Ah, I think I sent it by private mail, so it won't be in patchwork.
> Here you are:
Ah, that explains it.
> dtc/libfdt: Add README clarifying licensing
>
> The fact the dtc are distributed together, but have different licenses
> can be a bit confusing. Several people have enquired as to what the
> deal is with the libfdt licensing, so this patch adds a README
> clarifying the situation with a rationale.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
After correcting the log-message English a bit, it was applied.
The fact that the dtc and libfdt are distributed together, but have
different licenses, can be a bit confusing. Several people have
enquired as to what the deal is with the libfdt licensing, so this
patch adds a README clarifying the situation with a rationale.
To be in agreement in the record, I too signed off on that patch.
Objections to either, please let me know!
Thanks,
jdl
prev parent reply other threads:[~2008-01-04 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 18:21 Outstanding DTC patches? Jon Loeliger
2008-01-03 4:48 ` David Gibson
2008-01-03 14:14 ` Jon Loeliger
2008-01-04 2:43 ` David Gibson
2008-01-04 14:38 ` Jon Loeliger [this message]
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=E1JAngj-0003ih-Or@jdl.com \
--to=jdl@jdl.com \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.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.