All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 3.14.5
Date: Sun, 01 Jun 2014 16:46:52 +0100	[thread overview]
Message-ID: <538B4AEC.7010108@linicks.net> (raw)
In-Reply-To: <538B16C8.8090900@linicks.net>

On 01/06/14 13:04, Nick Warne wrote:
> I am getting hundreds of the same build warnings on this release -
> usually I get none - typical warnings:
>
> include/linux/sched.h:1691: warning: ‘pid_alive’ declared inline after
> being called
> include/linux/sched.h:1691: warning: previous declaration of ‘pid_alive’
> was here
>
> Info:
>
> Machine AMD64
> gcc version 4.2.4
>
> Any more info required please CC me.

OK, revisiting this between decorating, changing line 1691 in 
include/linux/sched.h to reflect 'inline':

from:
static int pid_alive(const struct task_struct *p);

to:
static inline int pid_alive(const struct task_struct *p);

stops GCC yelling at me.

Nick
-- 
"A bug in the code is worth two in the documentation."
FSF Associate Member 5508
http://linicks.net/
http://pi.linicks.net/

  reply	other threads:[~2014-06-01 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01 12:04 Linux 3.14.5 Nick Warne
2014-06-01 15:46 ` Nick Warne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-31 21:03 Greg KH
2014-05-31 21:03 ` 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=538B4AEC.7010108@linicks.net \
    --to=nick@linicks.net \
    --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 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.