From: Christian Brauner <christian.brauner@ubuntu.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christian Brauner <christian@brauner.io>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the pidfd tree
Date: Fri, 10 Jul 2020 09:59:06 +0200 [thread overview]
Message-ID: <20200710075906.dilvvpj3q5dij7fu@wittgenstein> (raw)
In-Reply-To: <20200710163204.651bb496@canb.auug.org.au>
On Fri, Jul 10, 2020 at 04:32:04PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the pidfd tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> fs/nsfs.c: In function 'ns_ioctl':
> fs/nsfs.c:195:14: warning: unused variable 'pid_struct' [-Wunused-variable]
> 195 | struct pid *pid_struct;
> | ^~~~~~~~~~
> fs/nsfs.c:194:22: warning: unused variable 'child_reaper' [-Wunused-variable]
> 194 | struct task_struct *child_reaper;
> | ^~~~~~~~~~~~
>
> Introduced by commit
>
> a57927d2dce2 ("nsfs: add NS_GET_INIT_PID ioctl")
Hm, I wonder how that didn't get caught during a git rebase -x "make" v5.8-rc4 build...
Sorry about that!
Thanks!
Christian
next prev parent reply other threads:[~2020-07-10 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 6:32 linux-next: build warning after merge of the pidfd tree Stephen Rothwell
2020-07-10 7:59 ` Christian Brauner [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-26 22:41 Stephen Rothwell
2021-01-27 7:12 ` Christoph Hellwig
2022-06-24 7:19 Stephen Rothwell
2022-06-24 7:19 Stephen Rothwell
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=20200710075906.dilvvpj3q5dij7fu@wittgenstein \
--to=christian.brauner@ubuntu.com \
--cc=christian@brauner.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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