From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: stop including i915_utils.h from intel_runtime_pm.h
Date: Thu, 12 Oct 2023 15:59:19 +0300 [thread overview]
Message-ID: <ZSftp5lhcopr-ehQ@intel.com> (raw)
In-Reply-To: <20231011162102.1030354-1-jani.nikula@intel.com>
On Wed, Oct 11, 2023 at 07:21:02PM +0300, Jani Nikula wrote:
> Remove an unnecessary include.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/intel_runtime_pm.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_runtime_pm.h b/drivers/gpu/drm/i915/intel_runtime_pm.h
> index f79cda7a2503..be43614c73fd 100644
> --- a/drivers/gpu/drm/i915/intel_runtime_pm.h
> +++ b/drivers/gpu/drm/i915/intel_runtime_pm.h
> @@ -11,8 +11,6 @@
>
> #include "intel_wakeref.h"
>
> -#include "i915_utils.h"
> -
> struct device;
> struct drm_i915_private;
> struct drm_printer;
> --
> 2.39.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-10-12 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 16:21 [Intel-gfx] [PATCH] drm/i915: stop including i915_utils.h from intel_runtime_pm.h Jani Nikula
2023-10-12 12:59 ` Ville Syrjälä [this message]
2023-10-13 2:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: stop including i915_utils.h from intel_runtime_pm.h (rev2) Patchwork
2023-10-13 2:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-14 1:08 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-14 15:31 ` [Intel-gfx] [PATCH] drm/i915: stop including i915_utils.h from intel_runtime_pm.h Andi Shyti
2023-10-23 12:14 ` Jani Nikula
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=ZSftp5lhcopr-ehQ@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.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