From: Jon Loeliger <jdl@jdl.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: ppc-dev list <linuxppc-dev@ozlabs.org>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: libfdt: Increase namespace-pollution paranoia
Date: Wed, 09 Jul 2008 08:09:02 -0500 [thread overview]
Message-ID: <E1KGZPq-0003YZ-T5@jdl.com> (raw)
In-Reply-To: <1F3AE758-B99A-457F-A74D-6D12DAF74115@kernel.crashing.org>
>
> > On a slightly unrelated note, are you planning to sync the in-kernel
> > dtc/libfdt version with the upstream version anytime soon?
>
> I know jon put an -rc, not sure if he plans to pick up the slew of
> patches for the next -rc or the next release, but it would be good to
> resync the in-kernel version for 2.6.27.
>
> - k
My (DTC) plan is to apply the single patch with some
include file fixes, and release that.
I'll line the slew of patches up for the following release.
jdl
next prev parent reply other threads:[~2008-07-09 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 4:10 libfdt: Increase namespace-pollution paranoia David Gibson
2008-07-09 11:42 ` Josh Boyer
2008-07-09 12:54 ` Kumar Gala
2008-07-09 13:09 ` Jon Loeliger [this message]
2008-07-14 19:02 ` Jon Loeliger
-- strict thread matches above, loose matches on Subject: below --
2008-07-14 19:08 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=E1KGZPq-0003YZ-T5@jdl.com \
--to=jdl@jdl.com \
--cc=david@gibson.dropbear.id.au \
--cc=galak@kernel.crashing.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox