Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/guc: Fix build break on config without DEBUG_FS
Date: Thu, 15 Mar 2018 08:49:20 -0700	[thread overview]
Message-ID: <20180315154920.GY3945@intel.com> (raw)
In-Reply-To: <20180315152848.40476-1-michal.wajdeczko@intel.com>

On Thu, Mar 15, 2018 at 03:28:47PM +0000, Michal Wajdeczko wrote:
> In commit 56b9a8b08387 ("drm/i915/guc: Update syntax of GuC
> log functions") we accidentally removed debugfs.h header
> where needed stub functions were defined.
> 
> Reported-by: Mike Lothian <mike@fireburn.co.uk>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Mike Lothian <mike@fireburn.co.uk>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>

Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

and pushed.

thanks for the patch.

> ---
>  drivers/gpu/drm/i915/intel_guc_log.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/intel_guc_log.c b/drivers/gpu/drm/i915/intel_guc_log.c
> index bfb9a68..1c2127b 100644
> --- a/drivers/gpu/drm/i915/intel_guc_log.c
> +++ b/drivers/gpu/drm/i915/intel_guc_log.c
> @@ -22,6 +22,8 @@
>   *
>   */
>  
> +#include <linux/debugfs.h>
> +
>  #include "intel_guc_log.h"
>  #include "i915_drv.h"
>  
> -- 
> 1.9.1
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-03-15 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 15:28 [PATCH] drm/i915/guc: Fix build break on config without DEBUG_FS Michal Wajdeczko
2018-03-15 15:49 ` Rodrigo Vivi [this message]
2018-03-15 16:05 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-03-15 20:22 ` ✓ Fi.CI.IGT: " Patchwork

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=20180315154920.GY3945@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michal.wajdeczko@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