From: Nick Warne <nick@linicks.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 3.14.5
Date: Sun, 01 Jun 2014 13:04:24 +0100 [thread overview]
Message-ID: <538B16C8.8090900@linicks.net> (raw)
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.
Nick
--
"A bug in the code is worth two in the documentation."
FSF Associate Member 5508
http://linicks.net/
http://pi.linicks.net/
next reply other threads:[~2014-06-01 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 12:04 Nick Warne [this message]
2014-06-01 15:46 ` Linux 3.14.5 Nick Warne
-- 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=538B16C8.8090900@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox