From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 2/2] drm: xe: xe_display_misc: fix build with W=1
Date: Tue, 24 Oct 2023 13:43:34 +0300 [thread overview]
Message-ID: <87zg089u7d.fsf@intel.com> (raw)
In-Reply-To: <20231020073430.103493-3-mauro.chehab@linux.intel.com>
On Fri, 20 Oct 2023, Mauro Carvalho Chehab <mauro.chehab@linux.intel.com> wrote:
> From: Mauro Carvalho Chehab <mchehab@kernel.org>
>
> As reported by LKP, when the Xe driver is built with W=1, a warning
> will be produced:
>
> >> drivers/gpu/drm/xe/display/xe_display_misc.c:10:14: warning: no previous prototype for 'intel_gmch_vga_set_decode' [-Wmissing-prototypes]
> 10 | unsigned int intel_gmch_vga_set_decode(struct pci_dev *pdev, bool enable_decode)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
>
> Currently, such function is just a stub, not used anywhere.
> Yet, it is declared there without a prototype. As this is just a
> reminder for something that will be implemented in the future,
> change it to static and add __maybe_unused to disable compiler
> warnings on it.
Please just include the header with the prototype.
BR,
Jani.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202310201234.ZZLwdoiy-lkp@intel.com/
> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
> drivers/gpu/drm/xe/display/xe_display_misc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/display/xe_display_misc.c b/drivers/gpu/drm/xe/display/xe_display_misc.c
> index 81ff97e704ea..53a53e500a09 100644
> --- a/drivers/gpu/drm/xe/display/xe_display_misc.c
> +++ b/drivers/gpu/drm/xe/display/xe_display_misc.c
> @@ -7,7 +7,7 @@
>
> struct pci_dev;
>
> -unsigned int intel_gmch_vga_set_decode(struct pci_dev *pdev, bool enable_decode)
> +__maybe_unused static unsigned int intel_gmch_vga_set_decode(struct pci_dev *pdev, bool enable_decode)
> {
> /* ToDo: Implement the actual handling of vga decode */
> return 0;
--
Jani Nikula, Intel
next prev parent reply other threads:[~2023-10-24 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 7:32 [Intel-xe] [PATCH 0/2] Fix two issues pointed by LKP Mauro Carvalho Chehab
2023-10-20 7:32 ` [Intel-xe] [PATCH 1/2] misc: mei: fix Kconfig dependencies Mauro Carvalho Chehab
2023-10-20 8:28 ` Francois Dugast
2023-10-24 10:52 ` Jani Nikula
2023-10-20 7:32 ` [Intel-xe] [PATCH 2/2] drm: xe: xe_display_misc: fix build with W=1 Mauro Carvalho Chehab
2023-10-24 10:43 ` Jani Nikula [this message]
2023-10-23 23:39 ` [Intel-xe] ✗ CI.Patch_applied: failure for Fix two issues pointed by LKP 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=87zg089u7d.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mauro.chehab@linux.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.