From: Kees Cook <keescook@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: James Morris <jmorris@namei.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warning after merge of the security tree
Date: Mon, 23 Apr 2012 08:23:48 -0700 [thread overview]
Message-ID: <CAGXu5j+KuoXLyjYZ2G9vS2XmHUKQ6diNGcV4XnEY+fOpS1DyQQ@mail.gmail.com> (raw)
In-Reply-To: <20120423165630.b412159ec0e5412ba41e0a98@canb.auug.org.au>
On Sun, Apr 22, 2012 at 11:56 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> After merging the security tree, today's linux-next build (powerpc
> allyesconfig) produced this warning:
>
> security/yama/yama_lsm.c:322:12: warning: 'one' defined but not used [-Wunused-variable]
>
> Introduced by commit 389da25f93ee ("Yama: add additional ptrace scopes").
Thanks! This has already been taken care of:
http://marc.info/?l=linux-security-module&m=133516581114617&w=2
-Kees
--
Kees Cook
Chrome OS Security
next prev parent reply other threads:[~2012-04-23 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 6:56 linux-next: build warning after merge of the security tree Stephen Rothwell
2012-04-23 15:23 ` Kees Cook [this message]
2014-08-04 6:25 Stephen Rothwell
2014-08-05 19:49 ` Paul Moore
2019-08-12 5:04 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=CAGXu5j+KuoXLyjYZ2G9vS2XmHUKQ6diNGcV4XnEY+fOpS1DyQQ@mail.gmail.com \
--to=keescook@chromium.org \
--cc=jmorris@namei.org \
--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;
as well as URLs for NNTP newsgroup(s).