mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Drokin, Oleg" <oleg.drokin@intel.com>
To: Ioan-Adrian Ratiu <adi@adirat.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	"<HPDD-discuss@lists.01.org>" <HPDD-discuss@ml01.01.org>,
	"<devel@driverdev.osuosl.org>" <devel@driverdev.osuosl.org>,
	"<linux-kernel@vger.kernel.org>" <linux-kernel@vger.kernel.org>
Subject: Re: [HPDD-discuss] [PATCH] staging: lustre: ptlrpc: add missing include directive
Date: Sat, 15 Aug 2015 10:11:06 +0000	[thread overview]
Message-ID: <5E37ED5E-2FE2-49BF-8B7F-A40C043D95FD@intel.com> (raw)
In-Reply-To: <20150815111339.6a9f7c34@adipc>

Hello!

On Aug 15, 2015, at 4:13 AM, Ioan-Adrian Ratiu wrote:

>>> Without including ptlrpc_internal.h, GCC gives prototype warnings
>>> "pack_generic.c:642:5: warning: no previous prototype for ..."
>> It does?  What version of gcc give you that, I don't see that here.
> Yes, but it's a non-default warning (-Wmissing-prototypes)
> 
> $ gcc --version
> gcc (Gentoo 4.9.3 p1.0, pie-0.6.2) 4.9.3
> 
> When testing the above patch I've used Ubuntu Vivid Vervet's gcc
> (also 4.9 I think, I don't have access to that machine right now).
> 
> To see the warn I'm adding "ccflags-y := -Wmissing-prototypes"
> to a Makefile then "make SUBDIRS=…"

Duh, so essentially it tells you that you have a non-static function
that lacks a previously defined prototype, but because it's
non-static, it's likely used elsewhere and the prototype might get
out of sync with the actual function definition?

I guess it's no big deal to include the ptlrpc_internal.h there
to catch potential problems like that.

Thanks.

Bye,
    Oleg

  reply	other threads:[~2015-08-15 10:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14  9:57 Ioan-Adrian Ratiu
2015-08-15  1:50 ` Greg KH
2015-08-15  8:13   ` Ioan-Adrian Ratiu
2015-08-15 10:11     ` Drokin, Oleg [this message]
2015-08-15 16:11     ` Greg KH

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=5E37ED5E-2FE2-49BF-8B7F-A40C043D95FD@intel.com \
    --to=oleg.drokin@intel.com \
    --cc=HPDD-discuss@ml01.01.org \
    --cc=adi@adirat.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®