From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Brauner <christian@brauner.io>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warning after merge of the pidfd-fixes tree
Date: Tue, 10 Mar 2020 08:07:58 +1100 [thread overview]
Message-ID: <20200310080758.0b7b6f6b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Hi all,
After merging the pidfd-fixes tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
In file included from include/linux/rwsem.h:18,
from include/linux/mm_types.h:11,
from include/linux/mmzone.h:21,
from include/linux/gfp.h:6,
from include/linux/mm.h:10,
from kernel/pid.c:30:
kernel/pid.c: In function 'alloc_pid':
include/linux/err.h:26:9: warning: 'retval' may be used uninitialized in this function [-Wmaybe-uninitialized]
26 | return (void *) error;
| ^~~~~~~~~~~~~~
kernel/pid.c:168:6: note: 'retval' was declared here
168 | int retval;
| ^~~~~~
Introduced by commit
8deb24dcb89c ("pid: make ENOMEM return value more obvious")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-03-09 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 21:07 Stephen Rothwell [this message]
2020-03-09 22:37 ` linux-next: build warning after merge of the pidfd-fixes tree Christian Brauner
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=20200310080758.0b7b6f6b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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