linux-edac.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Valdis Kletnieks <valdis.kletnieks@vt.edu>,
	Borislav Petkov <bp@suse.de>, Tony Luck <tony.luck@intel.com>,
	linux-edac@vger.kernel.org, x86@kernel.org,
	Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.2 078/313] RAS: Fix prototype warnings
Date: Thu, 3 Oct 2019 18:45:27 +0200	[thread overview]
Message-ID: <20191003164527.GB11675@zn.tnic> (raw)
In-Reply-To: <20191003154540.526612763@linuxfoundation.org>

On Thu, Oct 03, 2019 at 05:50:56PM +0200, Greg Kroah-Hartman wrote:
> From: Valdis Klētnieks <valdis.kletnieks@vt.edu>
> 
> [ Upstream commit 0a54b809a3a2c31e1055b45b03708eb730222be1 ]
> 
> When building with C=2 and/or W=1, legitimate warnings are issued about
> missing prototypes:
> 
>     CHECK   drivers/ras/debugfs.c
>   drivers/ras/debugfs.c:4:15: warning: symbol 'ras_debugfs_dir' was not declared. Should it be static?
>   drivers/ras/debugfs.c:8:5: warning: symbol 'ras_userspace_consumers' was not declared. Should it be static?
>   drivers/ras/debugfs.c:38:12: warning: symbol 'ras_add_daemon_trace' was not declared. Should it be static?
>   drivers/ras/debugfs.c:54:13: warning: symbol 'ras_debugfs_init' was not declared. Should it be static?
>     CC      drivers/ras/debugfs.o
>   drivers/ras/debugfs.c:8:5: warning: no previous prototype for 'ras_userspace_consumers' [-Wmissing-prototypes]
>       8 | int ras_userspace_consumers(void)
>         |     ^~~~~~~~~~~~~~~~~~~~~~~
>   drivers/ras/debugfs.c:38:12: warning: no previous prototype for 'ras_add_daemon_trace' [-Wmissing-prototypes]
>      38 | int __init ras_add_daemon_trace(void)
>         |            ^~~~~~~~~~~~~~~~~~~~
>   drivers/ras/debugfs.c:54:13: warning: no previous prototype for 'ras_debugfs_init' [-Wmissing-prototypes]
>      54 | void __init ras_debugfs_init(void)
>         |             ^~~~~~~~~~~~~~~~
> 
> Provide the proper includes.
> 
>  [ bp: Take care of the same warnings for cec.c too. ]
> 
> Signed-off-by: Valdis Kletnieks <valdis.kletnieks@vt.edu>
> Signed-off-by: Borislav Petkov <bp@suse.de>
> Cc: Tony Luck <tony.luck@intel.com>
> Cc: linux-edac@vger.kernel.org
> Cc: x86@kernel.org
> Link: http://lkml.kernel.org/r/7168.1565218769@turing-police
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
>  drivers/ras/cec.c     | 1 +
>  drivers/ras/debugfs.c | 2 ++
>  2 files changed, 3 insertions(+)
> 
> diff --git a/drivers/ras/cec.c b/drivers/ras/cec.c
> index f5795adc5a6e1..8037c490f3ba7 100644
> --- a/drivers/ras/cec.c
> +++ b/drivers/ras/cec.c
> @@ -1,6 +1,7 @@
>  // SPDX-License-Identifier: GPL-2.0
>  #include <linux/mm.h>
>  #include <linux/gfp.h>
> +#include <linux/ras.h>
>  #include <linux/kernel.h>
>  #include <linux/workqueue.h>
>  
> diff --git a/drivers/ras/debugfs.c b/drivers/ras/debugfs.c
> index 9c1b717efad86..0d4f985afbf37 100644
> --- a/drivers/ras/debugfs.c
> +++ b/drivers/ras/debugfs.c
> @@ -1,5 +1,7 @@
>  // SPDX-License-Identifier: GPL-2.0-only
>  #include <linux/debugfs.h>
> +#include <linux/ras.h>
> +#include "debugfs.h"
>  
>  struct dentry *ras_debugfs_dir;
>  
> -- 

Definitely not stable material.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2019-10-03 17:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191003154533.590915454@linuxfoundation.org>
2019-10-03 15:50 ` [PATCH 5.2 063/313] EDAC/mc: Fix grain_bits calculation Greg Kroah-Hartman
2019-10-03 15:50 ` [PATCH 5.2 071/313] EDAC/altera: Use the proper type for the IRQ status bits Greg Kroah-Hartman
2019-10-03 15:50 ` [PATCH 5.2 078/313] RAS: Fix prototype warnings Greg Kroah-Hartman
2019-10-03 16:45   ` Borislav Petkov [this message]
2019-10-03 18:17     ` Greg Kroah-Hartman
2019-10-03 15:50 ` [PATCH 5.2 079/313] RAS: Build debugfs.o only when enabled in Kconfig Greg Kroah-Hartman
2019-10-03 15:51 ` [PATCH 5.2 130/313] EDAC/amd64: Support more than two controllers for chip selects handling Greg Kroah-Hartman
2019-10-03 15:51 ` [PATCH 5.2 132/313] EDAC/amd64: Recognize DRAM device type ECC capability Greg Kroah-Hartman
2019-10-03 15:51 ` [PATCH 5.2 133/313] EDAC/amd64: Decode syndrome before translating address Greg Kroah-Hartman

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=20191003164527.GB11675@zn.tnic \
    --to=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=valdis.kletnieks@vt.edu \
    --cc=x86@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).