From: Greg KH <greg@kroah.com>
To: Nhan Nguyen <nhan.nguyen.yb@renesas.com>
Cc: stable@vger.kernel.org, Daniel Vetter <daniel.vetter@ffwll.ch>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Thong Ho <thong.ho.px@rvc.renesas.com>
Subject: Re: [PATCH 4.4.y 1/3] drm/rcar: Nuke preclose hook
Date: Thu, 3 Aug 2017 14:52:28 -0700 [thread overview]
Message-ID: <20170803215228.GA1988@kroah.com> (raw)
In-Reply-To: <20170720124948.6796-1-nhan.nguyen.yb@renesas.com>
On Thu, Jul 20, 2017 at 07:49:46PM +0700, Nhan Nguyen wrote:
> From: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> commit 0a346629f5304a8390004a91e8d4f1206b87792b upstream.
>
> Again since the drm core takes care of event unlinking/disarming this
> is now just needless code.
>
> This patch prepare for update "drm: rcar-du: Simplify and fix probe error handling"
>
> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Cc: stable@vger.kernel.org
> Acked-by: Daniel Stone <daniels@collabora.com>
> Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> Signed-off-by: Thong Ho <thong.ho.px@rvc.renesas.com>
> Signed-off-by: Nhan Nguyen <nhan.nguyen.yb@renesas.com>
> Link: http://patchwork.freedesktop.org/patch/msgid/1453756616-28942-10-git-send-email-daniel.vetter@ffwll.ch
> ---
> drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 20 --------------------
> drivers/gpu/drm/rcar-du/rcar_du_crtc.h | 2 --
> drivers/gpu/drm/rcar-du/rcar_du_drv.c | 10 ----------
> 3 files changed, 32 deletions(-)
All 3 now applied, thanks.
greg k-h
prev parent reply other threads:[~2017-08-03 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 12:49 [PATCH 4.4.y 1/3] drm/rcar: Nuke preclose hook Nhan Nguyen
2017-07-20 12:49 ` [PATCH 4.4.y 2/3] drm: rcar-du: Perform initialization/cleanup at probe/remove time Nhan Nguyen
2017-08-03 21:52 ` Greg KH [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=20170803215228.GA1988@kroah.com \
--to=greg@kroah.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=nhan.nguyen.yb@renesas.com \
--cc=stable@vger.kernel.org \
--cc=thong.ho.px@rvc.renesas.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.