From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
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 vfs tree
Date: Fri, 8 Sep 2017 08:53:54 +0300 [thread overview]
Message-ID: <20170908055353.GA8820@altlinux.org> (raw)
In-Reply-To: <20170908092545.15179b18@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
Hi,
On Fri, Sep 08, 2017 at 09:25:45AM +1000, Stephen Rothwell wrote:
> Hi Al,
>
> After merging the vfs tree, today's linux-next build (powerpc
> ppc64_defconfig) produced this warning:
>
> kernel/signal.c: In function 'C_SYSC_rt_sigaction':
> kernel/signal.c:3405:19: warning: unused variable 'mask' [-Wunused-variable]
> compat_sigset_t mask;
> ^
>
> Introduced by commit
>
> fc271087ebcb ("signal: replace sigset_to_compat() with put_compat_sigset()")
Thanks. The commit that made this variable unused is
9b24ec57688a ("get_compat_sigset()")
--
ldv
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-09-08 5:53 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 23:25 linux-next: build warning after merge of the vfs tree Stephen Rothwell
2017-09-08 5:53 ` Dmitry V. Levin [this message]
2017-09-14 1:51 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2021-04-12 11:47 Stephen Rothwell
2021-04-12 13:07 ` Miklos Szeredi
2021-04-15 21:19 ` Al Viro
2021-01-06 23:15 Stephen Rothwell
2021-01-07 0:37 ` Gao Xiang
2021-01-07 0:40 ` Al Viro
2020-09-24 1:40 Stephen Rothwell
2020-09-24 2:00 ` Al Viro
2020-06-16 0:21 Stephen Rothwell
2020-03-09 22:59 Stephen Rothwell
2020-03-09 23:17 ` Pali Rohár
2020-03-09 23:36 ` Namjae Jeon
2020-03-10 10:32 ` 'Greg Kroah-Hartman'
2019-02-03 22:33 Stephen Rothwell
2019-03-18 0:00 ` Stephen Rothwell
2019-03-25 23:05 ` Stephen Rothwell
2018-09-06 0:02 Stephen Rothwell
2018-09-07 8:57 ` David Howells
2018-06-19 1:53 Stephen Rothwell
2018-06-19 1:29 Stephen Rothwell
2018-05-17 0:39 Stephen Rothwell
2018-05-17 6:41 ` Christoph Hellwig
2018-05-14 0:56 Stephen Rothwell
2017-07-03 0:53 Stephen Rothwell
2017-07-09 23:34 ` Stephen Rothwell
2015-04-13 4:00 Stephen Rothwell
2012-10-12 5:06 Stephen Rothwell
2012-09-25 1:52 Stephen Rothwell
2012-01-05 6:35 Stephen Rothwell
2012-01-05 8:06 ` Al Viro
2012-01-05 8:14 ` Al Viro
2012-01-05 11:34 ` Jan Kara
2012-01-05 8:14 ` Stephen Rothwell
2012-01-05 8:19 ` Al Viro
2011-07-18 5:04 Stephen Rothwell
2011-07-18 5:17 ` Al Viro
2011-07-18 5:20 ` Al Viro
2010-07-05 0:01 Stephen Rothwell
2010-07-05 8:10 ` Al Viro
2010-07-05 10:44 ` Stephen Rothwell
2010-07-05 12:15 ` Jeff Layton
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=20170908055353.GA8820@altlinux.org \
--to=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@ZenIV.linux.org.uk \
/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.