From: Zack Rusin <zack.rusin@broadcom.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] drm/vmwgfx: Remove duplicate vmwgfx_vkms.h header
Date: Tue, 30 Apr 2024 12:58:01 -0400 [thread overview]
Message-ID: <CABQX2QPOoSPN5OHO_-sXxDEzUsTrKaicB4Xag3dw6BANbzjm_A@mail.gmail.com> (raw)
In-Reply-To: <20240417012917.66046-1-jiapeng.chong@linux.alibaba.com>
On Tue, Apr 16, 2024 at 9:29 PM Jiapeng Chong
<jiapeng.chong@linux.alibaba.com> wrote:
>
> ./drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c: vmwgfx_vkms.h is included more than once.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=8772
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c b/drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c
> index 7e93a45948f7..3bfcf671fcd5 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_vkms.c
> @@ -31,7 +31,6 @@
> #include "vmwgfx_bo.h"
> #include "vmwgfx_drv.h"
> #include "vmwgfx_kms.h"
> -#include "vmwgfx_vkms.h"
>
> #include "vmw_surface_cache.h"
>
> --
> 2.20.1.7.g153144c
Thanks. I pushed it to drm-misc-next.
z
prev parent reply other threads:[~2024-04-30 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 1:29 [PATCH] drm/vmwgfx: Remove duplicate vmwgfx_vkms.h header Jiapeng Chong
2024-04-30 16:58 ` Zack Rusin [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=CABQX2QPOoSPN5OHO_-sXxDEzUsTrKaicB4Xag3dw6BANbzjm_A@mail.gmail.com \
--to=zack.rusin@broadcom.com \
--cc=abaci@linux.alibaba.com \
--cc=airlied@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).