From: Stephen Rothwell <sfr@canb.auug.org.au>
To: John Johansen <john.johansen@canonical.com>
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 apparmor tree
Date: Thu, 23 Aug 2018 10:20:12 +1000 [thread overview]
Message-ID: <20180823102012.0c7cbe1c@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Hi John,
After merging the apparmor tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
security/apparmor/policy_unpack.c: In function 'unpack_dfa':
security/apparmor/policy_unpack.c:426:1: warning: label 'fail' defined but not used [-Wunused-label]
fail:
^~~~
Introduced by commit
fb5841091f28 ("apparmor: remove no-op permission check in policy_unpack")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2018-08-23 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 0:20 Stephen Rothwell [this message]
2018-08-23 1:46 ` linux-next: build warning after merge of the apparmor tree John Johansen
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=20180823102012.0c7cbe1c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=john.johansen@canonical.com \
--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