All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	Liviu Dudau <liviu.dudau@arm.com>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	James Qian Wang <james.qian.wang@arm.com>,
	Dave Airlie <airlied@redhat.com>,
	Mali DP Maintainers <malidp@foss.arm.com>,
	Lowry Li <lowry.li@arm.com>, Sean Paul <sean@poorly.run>
Subject: Re: [PATCH 5/5] RFC: MAINTAINERS: maintain drm/arm drivers in drm-misc for now
Date: Fri, 5 Jul 2019 14:31:01 +0200	[thread overview]
Message-ID: <20190705123101.purqrxvfzr2ifjkk@flea> (raw)
In-Reply-To: <20190705121006.26085-5-daniel.vetter@ffwll.ch>


[-- Attachment #1.1: Type: text/plain, Size: 1686 bytes --]

On Fri, Jul 05, 2019 at 02:10:06PM +0200, Daniel Vetter wrote:
> From discussions with Liviu it sounded like the komeda team would
> benefit a bit from more cross-review with other drivers. To make sure
> komeda is aligned with how similar problems are solved in other
> drivers (in the end everyone ends up with similar ideas on how to
> solve various display engine design issues).
>
> An option would be to use drm-misc as an incubator for a few kernel
> releases, at least until the big design items have been tackled: Aside
> from the four kms properties already landed that we need to take out
> again there's also a pile of new ones proposed already for komeda.
> drm-misc seems to work fairly well at encouraging these kind of
> cross-driver reviews and working on cross-driver infrastructure in drm
> core. Later on we can move all the drivers out to a dedicated arm tree
> again (if that's desired).
>
> Of coures that would mean Lowry and James need drm-misc commit rights
> (all other arm contributors have it already I think).
>
> Cc: Lowry Li (Arm Technology China) <lowry.li@arm.com>
> Cc: James Qian Wang (Arm Technology China) <james.qian.wang@arm.com>
> Cc: Liviu Dudau <liviu.dudau@arm.com>
> Cc: Mali DP Maintainers <malidp@foss.arm.com>
> Cc: Brian Starkey <brian.starkey@arm.com>
> Cc: Dave Airlie <airlied@redhat.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Maxime Ripard <maxime.ripard@bootlin.com>
> Cc: Sean Paul <sean@poorly.run>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>

Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>

Maxime

--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-07-05 12:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05 12:10 [PATCH 1/5] drm/komeda: Remove clock ratio property Daniel Vetter
2019-07-05 12:10 ` [PATCH 2/5] drm/komeda: remove slave_planes property Daniel Vetter
2019-07-09  8:07   ` james qian wang (Arm Technology China)
2019-07-05 12:10 ` [PATCH 3/5] drm/komeda: remove img_enhancement property Daniel Vetter
2019-07-09  8:08   ` james qian wang (Arm Technology China)
2019-07-05 12:10 ` [PATCH 4/5] drm/komeda: Remove layer_split property Daniel Vetter
2019-07-09  8:08   ` james qian wang (Arm Technology China)
2019-07-05 12:10 ` [PATCH 5/5] RFC: MAINTAINERS: maintain drm/arm drivers in drm-misc for now Daniel Vetter
2019-07-05 12:31   ` Maxime Ripard [this message]
2019-07-05 13:57   ` Liviu Dudau
2019-07-08  4:57     ` james qian wang (Arm Technology China)
2019-07-09  8:06 ` [PATCH 1/5] drm/komeda: Remove clock ratio property james qian wang (Arm Technology China)

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=20190705123101.purqrxvfzr2ifjkk@flea \
    --to=maxime.ripard@bootlin.com \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=james.qian.wang@arm.com \
    --cc=liviu.dudau@arm.com \
    --cc=lowry.li@arm.com \
    --cc=malidp@foss.arm.com \
    --cc=sean@poorly.run \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.