public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	Simon Horman <horms@verge.net.au>,
	Ulrich Hecht <uli+renesas@fpond.eu>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 0/8] drm: rcar-du: Add Color Management Module (CMM)
Date: Tue, 5 Nov 2019 21:52:05 +0200	[thread overview]
Message-ID: <20191105195205.GB4869@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CAMuHMdWTCF30+JpztF-p-5JqHS5ALiAs5E0Jo82DCgpu99NZ7w@mail.gmail.com>

Hi Geert,

On Tue, Nov 05, 2019 at 05:14:20PM +0100, Geert Uytterhoeven wrote:
> On Thu, Oct 17, 2019 at 9:14 PM Laurent Pinchart wrote:
> > On Wed, Oct 16, 2019 at 10:55:40AM +0200, Jacopo Mondi wrote:
> > > Minimal increment to the CMM series, this time should really be the last one.
> > >
> > > Just missing Rob's ack on [1/8] and Laurent's one on [5/8].
> > >
> > > Changelog is minimal:
> > > CMM
> > > - Remove the cmm_config.enable flag. The cmm_config.table field validity is
> > >   used to enable/disable the LUT operations
> > > - Expand comments as suggested by Laurent
> > >
> > > CRTC
> > > - use drm_color_lut_size() to check the LUT table size
> > > - Inline calls to rcar_cmm_enable()/disable()
> > > - Add TODO entries as suggested by Laurent
> > >
> > > For the record, the full series changelog is available at:
> > > https://paste.debian.net/1107427/
> > >
> > > v5 from yesterday with informations on testing is available at:
> > > https://lkml.org/lkml/2019/10/15/337
> > >
> > > Geert will you collect for DTS patches for the next release?
> > > I assume the DU changes go through Laurent instead ?
> >
> > I've taken patch 1/8 to 6/8 and 8/8 in my tree. I expected Geert to take
> > 7/8.
> 
> And so I did. 7/8 is now in arm-soc/for-next.
> 
> However, your drm/du/next branch seems to contain 7/8 instead of 8/8?

That was a mistake that I fixed in a second pull request (see
https://lists.freedesktop.org/archives/dri-devel/2019-October/241110.html),
I forgot to update the drm/du/next branch, but the tag should be
correct. I've now fixed the problem in the branch as well.

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2019-11-05 19:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-16  8:55 [PATCH v6 0/8] drm: rcar-du: Add Color Management Module (CMM) Jacopo Mondi
2019-10-16  8:55 ` [PATCH v6 1/8] dt-bindings: display: renesas,cmm: Add R-Car CMM documentation Jacopo Mondi
2019-10-17 14:10   ` Rob Herring
2019-10-16  8:55 ` [PATCH v6 2/8] dt-bindings: display, renesas,du: Document cmms property Jacopo Mondi
2019-10-16  8:55 ` [PATCH v6 3/8] drm: rcar-du: Add support for CMM Jacopo Mondi
2019-10-16 13:45   ` Laurent Pinchart
2019-10-17 12:43     ` Jacopo Mondi
2019-10-17 12:48       ` Laurent Pinchart
2019-10-17 13:43   ` [PATCH 6.1 " Jacopo Mondi
2019-10-17 19:11     ` Laurent Pinchart
2019-10-16  8:55 ` [PATCH v6 4/8] drm: rcar-du: kms: Initialize CMM instances Jacopo Mondi
2019-10-16  8:55 ` [PATCH v6 5/8] drm: rcar-du: crtc: Control CMM operations Jacopo Mondi
2019-10-16 13:49   ` Laurent Pinchart
2019-10-17 13:44   ` [PATCH v6.1 " Jacopo Mondi
2019-10-17 19:12     ` Laurent Pinchart
2019-10-16  8:55 ` [PATCH v6 6/8] drm: rcar-du: crtc: Register GAMMA_LUT properties Jacopo Mondi
2019-10-16  8:55 ` [PATCH v6 7/8] arm64: dts: renesas: Add CMM units to Gen3 SoCs Jacopo Mondi
2019-10-21  8:58   ` Geert Uytterhoeven
2019-10-16  8:55 ` [PATCH v6 8/8] drm: rcar-du: kms: Expand comment in vsps parsing routine Jacopo Mondi
2019-10-17 19:14 ` [PATCH v6 0/8] drm: rcar-du: Add Color Management Module (CMM) Laurent Pinchart
2019-11-05 16:14   ` Geert Uytterhoeven
2019-11-05 19:52     ` Laurent Pinchart [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=20191105195205.GB4869@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=jacopo+renesas@jmondi.org \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=uli+renesas@fpond.eu \
    /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