linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: tiantao6 <tiantao6@huawei.com>
Cc: tony.luck@intel.com, linux-edac@vger.kernel.org,
	linuxarm@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ras: debugfs: Fix warning: no previous prototype
Date: Tue, 10 Sep 2019 10:39:40 +0200	[thread overview]
Message-ID: <20190910083940.GC23931@zn.tnic> (raw)
In-Reply-To: <1568103739-36667-1-git-send-email-tiantao6@huawei.com>

On Tue, Sep 10, 2019 at 04:22:19PM +0800, tiantao6 wrote:
> fixed the fellow warning when building with warnings enabled (W=1)

"fellow"?

> 
> drivers/ras/debugfs.c:8:5: warning: no previous prototype for
> ‘ras_userspace_consumers’ [-Wmissing-prototypes]
> int ras_userspace_consumers(void)
> 
> drivers/ras/debugfs.c:38:12: warning: no previous prototype for
> ‘ras_add_daemon_trace’ [-Wmissing-prototypes]
> int __init ras_add_daemon_trace(void)
> 
> drivers/ras/debugfs.c:54:13: warning: no previous prototype for
> ‘ras_debugfs_init’ [-Wmissing-prototypes]
> void __init ras_debugfs_init(void)

https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=ras/core&id=0a54b809a3a2c31e1055b45b03708eb730222be1

> 
> Signed-off-by: tiantao6 <tiantao6@huawei.com>

Also, if you intend to send more patches in the future, please use your
real name.

Thx.

-- 
Regards/Gruss,
    Boris.

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

      reply	other threads:[~2019-09-10  8:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-10  8:22 [PATCH] ras: debugfs: Fix warning: no previous prototype tiantao6
2019-09-10  8:39 ` Borislav Petkov [this message]

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=20190910083940.GC23931@zn.tnic \
    --to=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=tiantao6@huawei.com \
    --cc=tony.luck@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;
as well as URLs for NNTP newsgroup(s).