From: Florian Fainelli <f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
Ian Campbell
<ian.campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
Subject: Re: [RFC] Culling traffic volume on devicetree mailing list
Date: Wed, 22 Jan 2014 08:05:20 -0800 [thread overview]
Message-ID: <5433179.eNHenyFL08@lenovo> (raw)
In-Reply-To: <CACxGe6vYMOnyeqdhaAggytxgiLH=ijNOrmuq2FyOUtZCGqfdgQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi,
Le mardi 21 janvier 2014, 14:40:48 Grant Likely a écrit :
> Hi everyone,
>
> Today on the devicetree conf call we (Rob, Ian and I) talked about
> culling the volume of traffic on the devicetree list so that it would
> be more useful to the DTC maintainers and non-Linux users like
> freebsd. We'd like to propose creating the following two lists so that
> those interested don't need to drink from the firehose:
>
> devicetree-compiler: Specifically for discussing dt tooling topics
> (parsing, schema validation, data format)
>
> devicetree-spec: For discussing 'core' device tree bindings. ie.
> anything that would be a candidate for putting into an ePAPR type
> spec. Individual device bindings would continue to be posted to
> devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, but anything affecting subsystems or
> generic patterns should be posted to this new list.
>
> Thoughts?
I definitively support that idea. Any schedule on when you plan on creating
those two mailing-lists?
--
Florian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-01-22 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 14:40 [RFC] Culling traffic volume on devicetree mailing list Grant Likely
[not found] ` <CACxGe6vYMOnyeqdhaAggytxgiLH=ijNOrmuq2FyOUtZCGqfdgQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-22 16:05 ` Florian Fainelli [this message]
2014-01-24 11:06 ` Grant Likely
2014-01-22 17:22 ` Jason Cooper
[not found] ` <20140122172243.GC29184-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2014-01-24 11:11 ` Grant Likely
2014-01-22 18:35 ` Olof Johansson
[not found] ` <CAOesGMhYfWXCFOc6K67aAcNNRUppONY4WNXTvk2NEJH-rfMrGQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-23 11:03 ` Ian Campbell
2014-01-24 11:13 ` Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2014-01-23 14:53 Rob Herring
[not found] <CAL_JsqL7SHFB2Pg6u0+1ZdeDSRaBS5S_=K8gWGcjbq3MpgyvFw@mail.gmail .com>
[not found] ` <CAL_JsqL7SHFB2Pg6u0+1ZdeDSRaBS5S_=K8gWGcjbq3MpgyvFw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-04 14:08 ` Grant Likely
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=5433179.eNHenyFL08@lenovo \
--to=f.fainelli-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=ian.campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@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;
as well as URLs for NNTP newsgroup(s).