[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <377a18ac-ca0d-75ba-7a50-0876dabfc1ed@infradead.org>
Date: Fri, 27 Nov 2020 11:12:10 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Peter Collingbourne <pcc@...gle.com>,
Helge Deller <deller@....de>, linux-parisc@...r.kernel.org,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: linux-next: Tree for Nov 27 (parisc: signal flags)
[adding Eric]
On 11/27/20 10:43 AM, Randy Dunlap wrote:
> On 11/27/20 1:04 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20201126:
>>
>
> on parisc, _SA_SIGGFAULT is undefined and causing build errors.
>
> commit 23acdc76f1798b090bb9dcc90671cd29d929834e
> Author: Peter Collingbourne <pcc@...gle.com>
> Date: Thu Nov 12 18:53:34 2020 -0800
>
> signal: clear non-uapi flag bits when passing/returning sa_flags
>
>
>
> _SA_SIGGFAULT is not used or defined anywhere else in the
> kernel source tree.
Here is the build error (although it should be obvious):
../kernel/signal.c: In function 'do_sigaction':
../arch/parisc/include/asm/signal.h:24:30: error: '_SA_SIGGFAULT' undeclared (first use in this function)
24 | #define __ARCH_UAPI_SA_FLAGS _SA_SIGGFAULT
| ^~~~~~~~~~~~~
--
~Randy
Reported-by: Randy Dunlap <rdunlap@...radead.org>
Powered by blists - more mailing lists