public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: Thoughts on removing this declaration
Date: Fri, 09 Aug 2013 07:21:58 +0000	[thread overview]
Message-ID: <20130809072158.GG5502@mwanda> (raw)
In-Reply-To: <201308082332.r78NWRBq272176@rivendell.pollux.laing>

On Thu, Aug 08, 2013 at 05:32:27PM -0600, Shaun Laing wrote:
> Hello -- what are your thoughts on this patch?  SBE_INCLUDE_SYMBOLS came out
> easily... too easily really.  Was it there on purpose?
> 

Yeah.  It's unfortunately a common thing.  :/  I'm not sure how it
is useful.

> 
> Removed the unused SBE_INCLUDE_SYMBOLS #define, and the associated STATIC
> #define, and replaced all occurances of STATIC with 'static'.  This was in
> response to sparse warnings of the form "symbol 'XYZ' was not declared. Should
> it be static?". 
> 

It is unneeded but it's not unused, it's always defined for
everything.  When SBE_INCLUDE_SYMBOLS is defined it makes the STATIC
disappear.

> Also had to add #ifdef around a function prototype as the 'static' declaration
> produced a new gcc warning, as the actual function was not defined.

The function is defined, of course, as you know.  The forward
declaration isn't needed.  Just remove it instead of adding the
ifdef.

Looks good, though.  Could you tweak the changelog, and remove the
prototype and resend?

regards,
dan carpenter


      reply	other threads:[~2013-08-09  7:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08 23:32 Thoughts on removing this declaration Shaun Laing
2013-08-09  7:21 ` Dan Carpenter [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=20130809072158.GG5502@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=kernel-janitors@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