All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qian Cai <cai@lca.pw>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: kieran.bingham+renesas@ideasonboard.com, airlied@linux.ie,
	daniel@ffwll.ch, dri-devel@lists.freedesktop.org,
	linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] drm/rcar-du: DRM_RCAR_WRITEBACK depends on DRM
Date: Fri, 21 Aug 2020 21:20:37 -0400	[thread overview]
Message-ID: <20200822012036.GA26224@lca.pw> (raw)
In-Reply-To: <20200608031622.GQ22208@pendragon.ideasonboard.com>

On Mon, Jun 08, 2020 at 06:16:22AM +0300, Laurent Pinchart wrote:
> Hi Qian,
> 
> I forgot to mention, I think the subject line should be
> 
> drm/rcar-du: Make DRM_RCAR_WRITEBACK depend on DRM_RCAR_DU
> 
> Could you please let me know if you're OK with these two small changes ?

Laurent, this patch is still not in the latest linux-next. Can you take a look?

> 
> On Mon, Jun 08, 2020 at 06:14:43AM +0300, Laurent Pinchart wrote:
> > On Sun, Jun 07, 2020 at 10:53:40PM -0400, Qian Cai wrote:
> > > There is no need to select DRM_RCAR_WRITEBACK if DRM=n which just make
> > 
> > s/DRM=n/DRM_RCAR_DU=n/ here.
> > 
> > > the generated .config a bit ugly.
> > > 
> > >  # ARM devices
> > >  #
> > >  # end of ARM devices
> > > 
> > >  CONFIG_DRM_RCAR_WRITEBACK=y
> > > 
> > >  #
> > >  # Frame buffer Devices
> > > 
> > > Let DRM_RCAR_WRITEBACK depend on DRM_RCAR_DU instead.
> > > 
> > > Signed-off-by: Qian Cai <cai@lca.pw>
> > 
> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > 
> > No need to submit a v3 if you agree with the above change, I'll fix it
> > in my tree.
> > 
> > > ---
> > >  drivers/gpu/drm/rcar-du/Kconfig | 1 +
> > >  1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/drivers/gpu/drm/rcar-du/Kconfig b/drivers/gpu/drm/rcar-du/Kconfig
> > > index 0919f1f159a4..3304b41f5611 100644
> > > --- a/drivers/gpu/drm/rcar-du/Kconfig
> > > +++ b/drivers/gpu/drm/rcar-du/Kconfig
> > > @@ -48,3 +48,4 @@ config DRM_RCAR_VSP
> > >  config DRM_RCAR_WRITEBACK
> > >  	bool
> > >  	default y if ARM64
> > > +	depends on DRM_RCAR_DU
> 
> -- 
> Regards,
> 
> Laurent Pinchart

WARNING: multiple messages have this Message-ID (diff)
From: Qian Cai <cai@lca.pw>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: airlied@linux.ie, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	linux-renesas-soc@vger.kernel.org,
	kieran.bingham+renesas@ideasonboard.com
Subject: Re: [PATCH v2] drm/rcar-du: DRM_RCAR_WRITEBACK depends on DRM
Date: Fri, 21 Aug 2020 21:20:37 -0400	[thread overview]
Message-ID: <20200822012036.GA26224@lca.pw> (raw)
In-Reply-To: <20200608031622.GQ22208@pendragon.ideasonboard.com>

On Mon, Jun 08, 2020 at 06:16:22AM +0300, Laurent Pinchart wrote:
> Hi Qian,
> 
> I forgot to mention, I think the subject line should be
> 
> drm/rcar-du: Make DRM_RCAR_WRITEBACK depend on DRM_RCAR_DU
> 
> Could you please let me know if you're OK with these two small changes ?

Laurent, this patch is still not in the latest linux-next. Can you take a look?

> 
> On Mon, Jun 08, 2020 at 06:14:43AM +0300, Laurent Pinchart wrote:
> > On Sun, Jun 07, 2020 at 10:53:40PM -0400, Qian Cai wrote:
> > > There is no need to select DRM_RCAR_WRITEBACK if DRM=n which just make
> > 
> > s/DRM=n/DRM_RCAR_DU=n/ here.
> > 
> > > the generated .config a bit ugly.
> > > 
> > >  # ARM devices
> > >  #
> > >  # end of ARM devices
> > > 
> > >  CONFIG_DRM_RCAR_WRITEBACK=y
> > > 
> > >  #
> > >  # Frame buffer Devices
> > > 
> > > Let DRM_RCAR_WRITEBACK depend on DRM_RCAR_DU instead.
> > > 
> > > Signed-off-by: Qian Cai <cai@lca.pw>
> > 
> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > 
> > No need to submit a v3 if you agree with the above change, I'll fix it
> > in my tree.
> > 
> > > ---
> > >  drivers/gpu/drm/rcar-du/Kconfig | 1 +
> > >  1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/drivers/gpu/drm/rcar-du/Kconfig b/drivers/gpu/drm/rcar-du/Kconfig
> > > index 0919f1f159a4..3304b41f5611 100644
> > > --- a/drivers/gpu/drm/rcar-du/Kconfig
> > > +++ b/drivers/gpu/drm/rcar-du/Kconfig
> > > @@ -48,3 +48,4 @@ config DRM_RCAR_VSP
> > >  config DRM_RCAR_WRITEBACK
> > >  	bool
> > >  	default y if ARM64
> > > +	depends on DRM_RCAR_DU
> 
> -- 
> Regards,
> 
> Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-08-22  1:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08  2:53 [PATCH v2] drm/rcar-du: DRM_RCAR_WRITEBACK depends on DRM Qian Cai
2020-06-08  2:53 ` Qian Cai
2020-06-08  3:14 ` Laurent Pinchart
2020-06-08  3:14   ` Laurent Pinchart
2020-06-08  3:16   ` Laurent Pinchart
2020-06-08  3:16     ` Laurent Pinchart
2020-06-08  4:30     ` Qian Cai
2020-06-08  4:30       ` Qian Cai
2020-06-10  9:24       ` Kieran Bingham
2020-06-10  9:24         ` Kieran Bingham
2020-08-22  1:20     ` Qian Cai [this message]
2020-08-22  1:20       ` Qian Cai
2020-08-23 22:18       ` Laurent Pinchart
2020-08-23 22:18         ` Laurent Pinchart

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=20200822012036.GA26224@lca.pw \
    --to=cai@lca.pw \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-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 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.