From: Sean Paul <sean@poorly.run>
To: Sabyasachi Gupta <sabyasachi.linux@gmail.com>
Cc: robdclark@gmail.com, airlied@linux.ie, seanpaul@chromium.org,
jsanka@codeaurora.org, jcrouse@codeaurora.org,
chandanu@codeaurora.org, jrdr.linux@gmail.com,
linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/msm/dpu: Remove duplicate header
Date: Wed, 15 May 2019 14:37:12 -0400 [thread overview]
Message-ID: <20190515183712.GZ17077@art_vandelay> (raw)
In-Reply-To: <5cda6de6.1c69fb81.a3ae5.836a@mx.google.com>
On Tue, May 14, 2019 at 12:57:28PM +0530, Sabyasachi Gupta wrote:
> Remove dpu_kms.h which is included more than once
>
> Signed-off-by: Sabyasachi Gupta <sabyasachi.linux@gmail.com>
Thanks for your patch, I've applied it to drm-misc-next-fixes.
Note for next time: The patch didn't apply cleanly since dpu_dbg.h has been
removed upstream. In future please make sure your patches apply cleanly and
at least build against upstream.
Thanks again!
Sean
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_hw_lm.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_lm.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_lm.c
> index dbe48e00..d692dee 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_lm.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_hw_lm.c
> @@ -16,7 +16,6 @@
> #include "dpu_hw_lm.h"
> #include "dpu_hw_mdss.h"
> #include "dpu_dbg.h"
> -#include "dpu_kms.h"
>
> #define LM_OP_MODE 0x00
> #define LM_OUT_SIZE 0x04
> --
> 2.7.4
>
--
Sean Paul, Software Engineer, Google / Chromium OS
prev parent reply other threads:[~2019-05-15 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 7:27 [PATCH] drm/msm/dpu: Remove duplicate header Sabyasachi Gupta
2019-05-15 18:37 ` Sean Paul [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=20190515183712.GZ17077@art_vandelay \
--to=sean@poorly.run \
--cc=airlied@linux.ie \
--cc=chandanu@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jcrouse@codeaurora.org \
--cc=jrdr.linux@gmail.com \
--cc=jsanka@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sabyasachi.linux@gmail.com \
--cc=seanpaul@chromium.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.