Linux Samsung SOC development
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Inki Dae <inki.dae@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PULL] drm-exynos-next 2014-12-22
Date: Thu, 8 Jan 2015 15:18:23 -0200	[thread overview]
Message-ID: <20150108171823.GD2001@joana> (raw)
In-Reply-To: <54AE06D1.9010105@samsung.com>

2015-01-08 Inki Dae <inki.dae@samsung.com>:

> On 2015년 01월 08일 03:06, Gustavo Padovan wrote:
> > 2014-12-26 Inki Dae <inki.dae@samsung.com>:
> >
> >> On 2014년 12월 22일 22:04, Gustavo Padovan wrote:
> >>> Hi Dave,
> >>>
> >>> Here goes a bunch of clean up for the exynos driver. I've posted this work in
> >>> the mailing list twice but never got a review on it, first time was about a
> >>
> >> Never no. I already had a review and they - your first time patch set -
> >> had been merged to exynos-drm-next-todo. I was moving them to
> >> exynos-drm-next locally but one of your patch set was not reasonable to
> >> me so I gave you one comment. After that, you posted next patch set
> >> which include new changes and patches just 9 days ago. So they should
> >> also be reviewed enough at least for two weeks.
> >
> > So please notify on the mailing list what you are doing. To me it looked that
> > all patches but one didn't get any review. I have a lot of pending work to do
> > on top of this pull request and review on them is quite important for me to
> > keep working on new changes.
> >
> >>
> >> Please, do not hurry. Such big changes should really be reviewed enough.
> >> I will wait for other reviews and them merge them if reviewed enough. If
> >> nobody have reviews then I will merge them. So please, don't worry about
> >> that.
> >
> > It is been a way more than two weeks now, can you please merge all my
> > patches but the 3 ones you had commented on? I'll send updated patches for
> > those.
> 
> Actually, I am waiting for your reply because your second patch series
> includes the changes and updates related to atomic page flip and mode
> setting, which doesn't have consistency with your first patch series.
> Anyway, I'll merge the only cleanup parts to exynos-drm-next. Please,
> post atomic parts after updating later. In addition, I'll not merge
> '[PATCH 01/29] drm/exynos/fimd: only finish pageflip if START ==
> START_S' because not clear to me as I already mentioned before.

Thank you. Yes, If you merge all the patches on this pull request I'll be fine
with it. It has only the clean ups.

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

      reply	other threads:[~2015-01-08 17:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22 13:04 [PULL] drm-exynos-next 2014-12-22 Gustavo Padovan
2014-12-26  1:18 ` Inki Dae
2015-01-07 18:06   ` Gustavo Padovan
2015-01-08  4:25     ` Inki Dae
2015-01-08 17:18       ` Gustavo Padovan [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=20150108171823.GD2001@joana \
    --to=gustavo@padovan.org \
    --cc=dri-devel@lists.freedesktop.org \
    --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