From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Collingbourne <pcc@google.com>,
Helge Deller <deller@gmx.de>,
linux-parisc@vger.kernel.org
Subject: Re: linux-next: Tree for Nov 27 (parisc: signal flags)
Date: Fri, 27 Nov 2020 10:43:07 -0800 [thread overview]
Message-ID: <155a20fd-09c4-df35-9cc6-8526a89c2933@infradead.org> (raw)
In-Reply-To: <20201127200457.1ffb6aaf@canb.auug.org.au>
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@google.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.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
next prev parent reply other threads:[~2020-11-27 18:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 9:04 linux-next: Tree for Nov 27 Stephen Rothwell
2020-11-27 15:57 ` linux-next: Tree for Nov 27 (drivers/idle/intel_idle.c) Randy Dunlap
2020-11-27 21:36 ` Stephen Rothwell
2020-11-27 21:38 ` Randy Dunlap
2020-11-30 11:54 ` Peter Zijlstra
2020-11-30 16:44 ` Randy Dunlap
2020-12-03 9:07 ` [tip: locking/urgent] intel_idle: Build fix tip-bot2 for Peter Zijlstra
2020-11-27 18:43 ` Randy Dunlap [this message]
2020-11-27 19:12 ` linux-next: Tree for Nov 27 (parisc: signal flags) Randy Dunlap
2020-11-27 21:44 ` Stephen Rothwell
2020-11-30 14:44 ` Eric W. Biederman
2020-11-30 17:30 ` [PATCH] signal/parics: Remove parsic specific definition of __ARCH_UAPI_SA_FLAGS Eric W. Biederman
2020-11-30 19:15 ` Randy Dunlap
2020-11-30 19:46 ` Eric W. Biederman
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=155a20fd-09c4-df35-9cc6-8526a89c2933@infradead.org \
--to=rdunlap@infradead.org \
--cc=deller@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=pcc@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.