From: Jani Nikula <jani.nikula@linux.intel.com>
To: Yang Li <yang.lee@linux.alibaba.com>, daniel@ffwll.ch
Cc: airlied@linux.ie, tvrtko.ursulin@linux.intel.com,
rodrigo.vivi@intel.com, joonas.lahtinen@linux.intel.com,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Yang Li <yang.lee@linux.alibaba.com>,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH -next 1/2] drm/i915: Remove duplicated include in intel_sseu.c
Date: Thu, 05 May 2022 13:18:43 +0300 [thread overview]
Message-ID: <87wnf0l1to.fsf@intel.com> (raw)
In-Reply-To: <20220504224816.41653-1-yang.lee@linux.alibaba.com>
On Thu, 05 May 2022, Yang Li <yang.lee@linux.alibaba.com> wrote:
> Fix following includecheck warning:
> ./drivers/gpu/drm/i915/gt/intel_sseu.c: linux/string_helpers.h is
> included more than once.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
Already fixed by commit 10dcf783f7e9 ("drm/i915: remove superfluous
string helper include").
BR,
Jani.
> ---
> drivers/gpu/drm/i915/gt/intel_sseu.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_sseu.c b/drivers/gpu/drm/i915/gt/intel_sseu.c
> index 9881a6790574..fdd25691beda 100644
> --- a/drivers/gpu/drm/i915/gt/intel_sseu.c
> +++ b/drivers/gpu/drm/i915/gt/intel_sseu.c
> @@ -10,8 +10,6 @@
> #include "intel_gt_regs.h"
> #include "intel_sseu.h"
>
> -#include "linux/string_helpers.h"
> -
> void intel_sseu_set_info(struct sseu_dev_info *sseu, u8 max_slices,
> u8 max_subslices, u8 max_eus_per_subslice)
> {
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2022-05-05 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 22:48 [PATCH -next 1/2] drm/i915: Remove duplicated include in intel_sseu.c Yang Li
2022-05-04 22:48 ` [PATCH -next 2/2] drm/i915/migrate: remove unneeded semicolon Yang Li
2022-05-05 10:18 ` Jani Nikula [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=87wnf0l1to.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=abaci@linux.alibaba.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
--cc=yang.lee@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox