From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [RFC] Allow device tree to be modified by additonal device tree sections
Date: Tue, 23 Feb 2010 21:57:37 -0700 [thread overview]
Message-ID: <fa686aa41002232057j45707ad0ofce684acc5680b6b@mail.gmail.com> (raw)
In-Reply-To: <20100224044220.GI7187@yookeroo>
On Tue, Feb 23, 2010 at 9:42 PM, David Gibson
<david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org> wrote:
> On Tue, Feb 23, 2010 at 07:05:53PM -0700, Grant Likely wrote:
>> On Tue, Feb 23, 2010 at 6:36 PM, David Gibson
>> <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org> wrote:
>> > On Tue, Feb 23, 2010 at 12:28:13PM -0700, Grant Likely wrote:
> [snip]
>> My opinion: no way. We're not working with real OF, and none of the
>> use cases I see have any need of such a feature. While we could
>> forbid it now and permit it later, we cannot permit it now and forbid
>> it later. I say no until someone comes up with a reasonable use case
>> on why it should be implemented.
>
> A sound argument. Done.
Okay, thanks for the feedback. I've rebased the patch onto your
multi-label patch and added support for merging labels. I'll properly
test it and repost tomorrow.
Cheers,
g.
prev parent reply other threads:[~2010-02-24 4:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 19:28 [RFC] Allow device tree to be modified by additonal device tree sections Grant Likely
2010-02-24 1:36 ` David Gibson
2010-02-24 2:05 ` Grant Likely
[not found] ` <fa686aa41002231805q1f5c6179j6fb7f6cd0558972e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-24 4:42 ` David Gibson
2010-02-24 4:57 ` Grant Likely [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=fa686aa41002232057j45707ad0ofce684acc5680b6b@mail.gmail.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@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