From: Robert Foss <robert.foss@collabora.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
Kalyan Kondapally <kalyan.kondapally@intel.com>,
Kaveh Nasri <kaveh.nasri@intel.com>,
Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Zach Reizner <zachr@chromium.org>,
Daniel Stone <daniels@collabora.com>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Marissa Wall <marissaw@google.com>,
Stephane Marchesin <marcheu@chromium.org>
Subject: Re: drm_hwcomposer moving to fd.o
Date: Fri, 22 Sep 2017 17:23:35 +0200 [thread overview]
Message-ID: <1506093815.2286.3.camel@collabora.com> (raw)
In-Reply-To: <87bmm3t1v9.fsf@intel.com>
Hey Jani,
On Fri, 2017-09-22 at 14:21 +0300, Jani Nikula wrote:
> On Fri, 22 Sep 2017, Robert Foss <robert.foss@collabora.com> wrote:
> > After talking to Liviu Dudau at LPC and Sean Paul & Kaveh Nasri at
> > XDC
> > it seems that we all could benefit from community maintainership of
> > drm_hwcomposer.
>
> Sounds good!
>
> > Regarding contributions, they are accepted on the dri-devel list,
> > using
> > the patch prefix "hwc".
>
> dri-devel averages around 2400-2500 messages per month AFAICT. If hwc
> community development picks up any kind of momentum, please consider
> starting a new list. Or would a joint userspace list with e.g. libdrm
> be
> beneficial? Daniel Stone will help you here.
A separate ML if there ends up being a significant volume of traffic
sounds like a good idea.
I guess we're following the IGT model here, and will move if/when
sustained development is occurring.
>
> BR,
> Jani.
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-09-22 15:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 23:52 drm_hwcomposer moving to fd.o Robert Foss
2017-09-22 2:40 ` Chih-Wei Huang
2017-09-22 15:43 ` Robert Foss
2017-09-25 2:44 ` Chih-Wei Huang
2017-09-25 3:25 ` Kondapally, Kalyan
2017-09-25 7:06 ` Tomeu Vizoso
2017-09-26 5:26 ` Daniel Vetter
2017-09-28 6:49 ` Chih-Wei Huang
2017-09-28 7:08 ` Daniel Vetter
2017-09-28 7:35 ` Tomeu Vizoso
2017-09-28 7:43 ` Tapani Pälli
2017-09-28 7:59 ` Daniel Vetter
2017-09-29 5:31 ` Chih-Wei Huang
2017-09-22 11:21 ` Jani Nikula
2017-09-22 15:23 ` Robert Foss [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=1506093815.2286.3.camel@collabora.com \
--to=robert.foss@collabora.com \
--cc=Liviu.Dudau@arm.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kalyan.kondapally@intel.com \
--cc=kaveh.nasri@intel.com \
--cc=marcheu@chromium.org \
--cc=marissaw@google.com \
--cc=tomeu.vizoso@collabora.com \
--cc=zachr@chromium.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