From: Stephen Rothwell <sfr@canb•auug.org.au>
To: John Johansen <john.johansen@canonical•com>
Cc: James Morris <jmorris@namei•org>,
Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: [PATCH] apparmor: fix build failure on sparc caused by undeclared, signals
Date: Thu, 24 Aug 2017 09:54:07 +1000 [thread overview]
Message-ID: <20170824095407.0825d469@canb.auug.org.au> (raw)
In-Reply-To: <40445189-181f-fc19-3c44-8fa2ab23d2f9@canonical.com>
Hi John,
On Wed, 23 Aug 2017 12:21:43 -0700 John Johansen <john.johansen@canonical•com> wrote:
>
> In file included from security/apparmor/ipc.c:23:0:
> security/apparmor/include/sig_names.h:26:3: error: 'SIGSTKFLT' undeclared here (not in a function)
> [SIGSTKFLT] = 16, /* -, 16, - */
> ^
> security/apparmor/include/sig_names.h:26:3: error: array index in initializer not of integer type
> security/apparmor/include/sig_names.h:26:3: note: (near initialization for 'sig_map')
> security/apparmor/include/sig_names.h:51:3: error: 'SIGUNUSED' undeclared here (not in a function)
> [SIGUNUSED] = 34, /* -, 31, - */
> ^
> security/apparmor/include/sig_names.h:51:3: error: array index in initializer not of integer type
> security/apparmor/include/sig_names.h:51:3: note: (near initialization for 'sig_map')
>
> Reported-by: Stephen Rothwell <sfr@canb•auug.org.au>
> Fixes: c6bf1adaecaa ("apparmor: add the ability to mediate signals")
> Signed-off-by: John Johansen <john.johansen@canonical•com>
I will apply this to linux-next today and will drop it when James picks
it up.
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-08-23 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 11:12 linux-next: build failure after merge of the security tree Stephen Rothwell
2017-08-23 19:21 ` [PATCH] apparmor: fix build failure on sparc caused by undeclared, signals John Johansen
2017-08-23 23:54 ` Stephen Rothwell [this message]
2017-08-24 1:16 ` James Morris
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=20170824095407.0825d469@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=jmorris@namei$(echo .)org \
--cc=john.johansen@canonical$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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