From: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH v3] Allow device tree to be modified by additonal device tree sections
Date: Fri, 26 Feb 2010 08:06:32 -0600 [thread overview]
Message-ID: <E1Nl0ps-00044Z-7b@jdl.com> (raw)
In-Reply-To: <20100226002554.GI31576@yookeroo>
>
> Oops, I was hoping to make a few tweaks to that before it was
> applied. Oh well, it was basically only more thorough testcases, so
> that can be added later.
Sorry -- I had no idea about that.
Follow up patches welcome, of course!
jdl
prev parent reply other threads:[~2010-02-26 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 16:58 [PATCH v3] Allow device tree to be modified by additonal device tree sections Grant Likely
2010-02-25 17:49 ` Jon Loeliger
[not found] ` <E1Nkhq1-0001Of-Hb-CYoMK+44s/E@public.gmane.org>
2010-02-26 0:25 ` David Gibson
2010-02-26 14:06 ` 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=E1Nl0ps-00044Z-7b@jdl.com \
--to=jdl-cyomk+44s/e@public.gmane.org \
--cc=david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@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