Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Inki Dae <inki.dae@samsung.com>,
	linux-samsung-soc <linux-samsung-soc@vger.kernel.org>,
	Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/4] removal of extra abstraction layers
Date: Mon, 8 Dec 2014 15:03:22 -0200	[thread overview]
Message-ID: <20141208170322.GA31894@joana> (raw)
In-Reply-To: <CAPM=9twYXeMJ-HRoC69SbDyz4Uu14Fz=9ZNmBGmWMS3mkG+c+g@mail.gmail.com>

Hi Inki,

2014-12-06 Dave Airlie <airlied@gmail.com>:

> On 2 December 2014 at 22:38, Gustavo Padovan <gustavo@padovan.org> wrote:
> > Hi Inki,
> >
> > Can you please review this? I also have sent other two patch sets that sits on
> > top of this one. Thanks.
> 
> Inki, any plans on when you can get to looking at this?
> 
> I think cleaning up exynos so we can get atomic using it is something
> that will benefit it heavily.

Besides these patches I have other two clean up patchsets[0][1] that are very
important for atomic support, can you review these two too?

[0] http://www.spinics.net/lists/linux-samsung-soc/msg39614.html
[1] http://www.spinics.net/lists/linux-samsung-soc/msg39632.html

	Gustavo

  reply	other threads:[~2014-12-08 17:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 18:21 [PATCH 0/4] removal of extra abstraction layers Gustavo Padovan
2014-11-24 18:21 ` [PATCH 1/4] drm/exynos: move to_exynos_crtc() macro to main header Gustavo Padovan
2014-11-24 18:21 ` [PATCH 2/4] drm/exynos: expose struct exynos_drm_crtc Gustavo Padovan
2014-11-24 18:21 ` [PATCH 3/4] drm/exynos: remove exynos_drm_crtc_plane_* wrappers Gustavo Padovan
2014-11-24 18:21 ` [PATCH 4/4] drm/exynos: remove struct exynos_drm_overlay Gustavo Padovan
2014-12-02 12:38 ` [PATCH 0/4] removal of extra abstraction layers Gustavo Padovan
2014-12-05 20:06   ` Dave Airlie
2014-12-08 17:03     ` Gustavo Padovan [this message]
2014-12-10 19:43       ` Daniel Stone

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=20141208170322.GA31894@joana \
    --to=gustavo@padovan.org \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gustavo.padovan@collabora.co.uk \
    --cc=inki.dae@samsung.com \
    --cc=linux-samsung-soc@vger.kernel.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