From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Sean MacLennan" <smaclennan@pikatech.com>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org, parch@power.org
Subject: Re: [ANN] Device Tree Mailing List
Date: Thu, 24 Jul 2008 15:07:55 -0400 [thread overview]
Message-ID: <fa686aa40807241207w42a70d8crd5f60c766a9550ef@mail.gmail.com> (raw)
In-Reply-To: <20080724145706.138af140@lappy.seanm.ca>
On Thu, Jul 24, 2008 at 2:57 PM, Sean MacLennan <smaclennan@pikatech.com> wrote:
> On Thu, 24 Jul 2008 14:36:09 -0400
> "Hugh Blemings" <hugh@blemings.org> wrote:
>
>> Hiya,
>>
>> Grant Likely and Josh Boyer organised a Bird of Feather session on
>> Device Trees today at the Ottawa Linux Symposium, about a dozen folk
>> there all told.
>>
>> Was agreed that there was now enough non-PowerPC specific interest in
>> Device Trees to make a generic list a useful thing to have, so have
>> gone ahead and got one set up;
>>
>> https://ozlabs.org/mailman/listinfo/devicetree-discuss
>>
>> For folk I knew to be interested/involved in DT stuff you may have
>> already received an invitation to join, I trust this was in order.
>>
>> If you didn't, please don't feel left out, I just did a quick off the
>> top of my head search through the mailing list archive :)
>
> I assume that powerpc specific device tree questions/patches can still
> be posted here though?
If it is related to bindings (even powerpc-specific bindings) I think
it is better to discuss them on the new list. Doing so helps keep
usage conventions consistent across all architectures.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2008-07-24 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 18:36 [ANN] Device Tree Mailing List Hugh Blemings
2008-07-24 18:57 ` Sean MacLennan
2008-07-24 19:07 ` 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=fa686aa40807241207w42a70d8crd5f60c766a9550ef@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=devicetree-discuss@ozlabs.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=parch@power.org \
--cc=smaclennan@pikatech.com \
/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;
as well as URLs for NNTP newsgroup(s).