From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/pxp: fix sparse warning for not declared symbol
Date: Wed, 8 Jun 2022 09:06:48 +0100 [thread overview]
Message-ID: <7b62505a-95a0-25ab-9299-e349453e49f5@linux.intel.com> (raw)
In-Reply-To: <20220506120405.2582372-1-jani.nikula@intel.com>
On 06/05/2022 13:04, Jani Nikula wrote:
> Fix:
>
> drivers/gpu/drm/i915/pxp/intel_pxp_debugfs.c:61:6: warning: symbol
> 'intel_pxp_debugfs_register' was not declared. Should it be static?
>
> Sort and remove the redundant pxp prefixes from the includes while at
> it.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/pxp/intel_pxp_debugfs.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/pxp/intel_pxp_debugfs.c b/drivers/gpu/drm/i915/pxp/intel_pxp_debugfs.c
> index c9da1015eb42..e888b5124a07 100644
> --- a/drivers/gpu/drm/i915/pxp/intel_pxp_debugfs.c
> +++ b/drivers/gpu/drm/i915/pxp/intel_pxp_debugfs.c
> @@ -9,9 +9,10 @@
> #include <drm/drm_print.h>
>
> #include "gt/intel_gt_debugfs.h"
> -#include "pxp/intel_pxp.h"
> -#include "pxp/intel_pxp_irq.h"
> #include "i915_drv.h"
> +#include "intel_pxp.h"
> +#include "intel_pxp_debugfs.h"
> +#include "intel_pxp_irq.h"
>
> static int pxp_info_show(struct seq_file *m, void *data)
> {
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Lets try to copy domain owners when doing cleanups to lessen the
maintainer load, since it appears people are not really scanning the
upstream mailing list these days. :(
Regards,
Tvrtko
next prev parent reply other threads:[~2022-06-08 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 12:04 [Intel-gfx] [PATCH] drm/i915/pxp: fix sparse warning for not declared symbol Jani Nikula
2022-05-06 13:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-05-06 14:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-05-06 16:49 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-06-08 8:06 ` Tvrtko Ursulin [this message]
2022-06-08 8:46 ` [Intel-gfx] [PATCH] " 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=7b62505a-95a0-25ab-9299-e349453e49f5@linux.intel.com \
--to=tvrtko.ursulin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.