All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Sean Paul <sean@poorly.run>
Cc: Xinliang Liu <z.liuxinliang@hisilicon.com>,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	David Airlie <airlied@linux.ie>,
	Chen Feng <puck.chen@hisilicon.com>,
	Alexey Brodkin <abrodkin@synopsys.com>,
	Philippe Cornu <philippe.cornu@st.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Vincent Abriou <vincent.abriou@st.com>,
	Hans de Goede <hdegoede@redhat.com>,
	Xinwei Kong <kong.kongxinwei@hisilicon.com>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Rongrong Zou <zourongrong@gmail.com>,
	Yannick Fertre <yannick.fertre@st.com>
Subject: Re: [PATCH v5 6/6] drm: remove drmP.h from drm_modeset_helper.h
Date: Thu, 24 Jan 2019 22:52:56 +0100	[thread overview]
Message-ID: <20190124215256.GA32543@ravnborg.org> (raw)
In-Reply-To: <20190124202840.GR114153@art_vandelay>

Hi Sean/Hans.

> > Hans de Goede sent out patches in September to convert it to a proper
> > atomic driver.
> > I recall that the feedback was mostly positive and that there was only
> > minor things to left to do. Hans?

I browsed the archieves and I could not find anything that was not addressed,
so nothing is apperantly missing expect the actual move from staging to gpu/drm/
And that move out of staging may require a proper review at dri-devel?

Browsing the code left me with an impression of a nice code base.

	Sam

      reply	other threads:[~2019-01-24 21:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19  8:40 [PATCH v5 0/6] drm: minimize drmP.h dependencies Sam Ravnborg
2019-01-19  8:40 ` Sam Ravnborg
2019-01-19  8:40 ` [PATCH v5 1/6] drm/stm: prepare for drmP.h removal from drm_modeset_helper.h Sam Ravnborg
2019-01-19  8:40   ` Sam Ravnborg
2019-01-19  8:40 ` [PATCH v5 2/6] drm/hisilicon/kirin: " Sam Ravnborg
2019-01-19  8:40   ` Sam Ravnborg
2019-01-19  8:40 ` [PATCH v5 3/6] drm/arcpgu: " Sam Ravnborg
2019-01-19  8:40   ` Sam Ravnborg
2019-01-19  8:40 ` [PATCH v5 4/6] drm/bridge: cdns: " Sam Ravnborg
2019-01-19  8:40   ` Sam Ravnborg
2019-01-19  8:40 ` [PATCH v5 5/6] drmi/rcar-du: " Sam Ravnborg
2019-01-19  8:40   ` Sam Ravnborg
2019-01-19  8:40 ` [PATCH v5 6/6] drm: remove drmP.h " Sam Ravnborg
2019-01-19  8:40   ` Sam Ravnborg
2019-01-24 14:03   ` Daniel Vetter
2019-01-24 14:03     ` Daniel Vetter
2019-01-24 14:44     ` Sam Ravnborg
2019-01-24 20:07     ` Sean Paul
2019-01-24 20:07       ` Sean Paul
2019-01-24 20:17       ` Sam Ravnborg
2019-01-24 20:17         ` Sam Ravnborg
2019-01-24 20:28         ` Sean Paul
2019-01-24 20:28           ` Sean Paul
2019-01-24 21:52           ` Sam Ravnborg [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=20190124215256.GA32543@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=abrodkin@synopsys.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=kong.kongxinwei@hisilicon.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@bootlin.com \
    --cc=philippe.cornu@st.com \
    --cc=puck.chen@hisilicon.com \
    --cc=sean@poorly.run \
    --cc=vincent.abriou@st.com \
    --cc=yannick.fertre@st.com \
    --cc=z.liuxinliang@hisilicon.com \
    --cc=zourongrong@gmail.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 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.