From: Helge Deller <deller@gmx.de>
To: Anders Roxell <anders.roxell@linaro.org>,
James.Bottomley@HansenPartnership.com
Cc: linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] parisc: signal: remove _SA_SIGGFAULT
Date: Thu, 26 Nov 2020 15:46:23 +0100 [thread overview]
Message-ID: <8affd609-f037-8b21-853a-8b87299db044@gmx.de> (raw)
In-Reply-To: <20201126130606.2290438-1-anders.roxell@linaro.org>
On 11/26/20 2:06 PM, Anders Roxell wrote:
> When building tinyconfig on parisc the following error shows up:
>
> /tmp/kernel/signal.c: In function 'do_sigaction':
> /tmp/arch/parisc/include/asm/signal.h:24:30: error: '_SA_SIGGFAULT' undeclared (first use in this function); did you mean 'SIL_FAULT'?
> #define __ARCH_UAPI_SA_FLAGS _SA_SIGGFAULT
> ^~~~~~~~~~~~~
>
> The changes in the two individual patches listed in 'Fixes' below are
> OK. Remove the _SA_SIGGFAULT define since PH-UX isn't going to be
> supported according to commit 41f5a81c07cd ("parisc: Drop HP-UX specific
> fcntl and signal flags").
>
> Fixes: 23acdc76f179 ("signal: clear non-uapi flag bits when passing/returning sa_flags")
> Fixes: 41f5a81c07cd ("parisc: Drop HP-UX specific fcntl and signal flags")
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> ---
> arch/parisc/include/asm/signal.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/arch/parisc/include/asm/signal.h b/arch/parisc/include/asm/signal.h
> index 30dd1e43ef88..715c96ba2ec8 100644
> --- a/arch/parisc/include/asm/signal.h
> +++ b/arch/parisc/include/asm/signal.h
> @@ -21,8 +21,6 @@ typedef struct {
> unsigned long sig[_NSIG_WORDS];
> } sigset_t;
>
> -#define __ARCH_UAPI_SA_FLAGS _SA_SIGGFAULT
> -
Which kernel are you testing?
I don't see this line in current git head...?!?
Helge
> #include <asm/sigcontext.h>
>
> #endif /* !__ASSEMBLY */
>
next prev parent reply other threads:[~2020-11-26 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 13:06 Anders Roxell
2020-11-26 14:46 ` Helge Deller [this message]
2020-11-26 22:39 ` Anders Roxell
2020-12-02 8:01 ` Naresh Kamboju
2020-12-15 14:24 ` Naresh Kamboju
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=8affd609-f037-8b21-853a-8b87299db044@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=anders.roxell@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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
all inboxes | Powered by JetHome®