From: Matthew Auld <matthew.auld@intel.com>
To: Ran Jianping <cgel.zte@gmail.com>
Cc: airlied@linux.ie, chris@chris-wilson.co.uk, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
linux-kernel@vger.kernel.org, maarten.lankhorst@linux.intel.com,
ran.jianping@zte.com.cn, rodrigo.vivi@intel.com,
thomas.hellstrom@linux.intel.com, zealci@zte.com.cn
Subject: Re: drm/i915: remove duplicate include in mock_region.c
Date: Wed, 20 Oct 2021 09:12:06 +0100 [thread overview]
Message-ID: <269d8cad-1379-ec7c-21f3-d73b7be1ec70@intel.com> (raw)
In-Reply-To: <20211020080401.1037442-1-ran.jianping@zte.com.cn>
On 20/10/2021 09:04, Ran Jianping wrote:
> From: ran jianping <ran.jianping@zte.com.cn>
>
> 'drm/ttm/ttm_placement.h' included in
> 'drivers/gpu/drm/i915/selftests/mock_region.c' is duplicated.
> It is also included on the 9 line.
>
> Reported-by: Zeal Robot <zealci@zte.com.cn>
> Signed-off-by: ran jianping <ran.jianping@zte.com.cn>
Pushed to drm-intel-gt-next. Thanks.
> ---
> drivers/gpu/drm/i915/selftests/mock_region.c | 2 --
> 1 file changed, 2 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/selftests/mock_region.c b/drivers/gpu/drm/i915/selftests/mock_region.c
> index efa86dffe3c6..b6747b3eeac5 100644
> --- a/drivers/gpu/drm/i915/selftests/mock_region.c
> +++ b/drivers/gpu/drm/i915/selftests/mock_region.c
> @@ -6,7 +6,5 @@
> #include <drm/ttm/ttm_placement.h>
> #include <linux/scatterlist.h>
>
> -#include <drm/ttm/ttm_placement.h>
> -
> #include "gem/i915_gem_region.h"
> #include "intel_memory_region.h"
>
prev parent reply other threads:[~2021-10-20 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 9:02 [PATCH] " cgel.zte
2021-10-19 9:26 ` Matthew Auld
2021-10-20 8:04 ` drm/i915: " Ran Jianping
2021-10-20 8:12 ` Matthew Auld [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=269d8cad-1379-ec7c-21f3-d73b7be1ec70@intel.com \
--to=matthew.auld@intel.com \
--cc=airlied@linux.ie \
--cc=cgel.zte@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=ran.jianping@zte.com.cn \
--cc=rodrigo.vivi@intel.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=zealci@zte.com.cn \
/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
all inboxes | Powered by JetHome®