From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-c6x-dev@linux-c6x.org, Jens Axboe <axboe@kernel.dk>,
Mark Salter <msalter@redhat.com>,
Aurelien Jacquiot <jacquiot.aurelien@gmail.com>
Subject: [PATCH -next] c6x: fix build of signal.c using _TIF_SIGNALs
Date: Wed, 9 Dec 2020 19:17:42 -0800 [thread overview]
Message-ID: <20201210031742.14534-1-rdunlap@infradead.org> (raw)
kernel/signal.c in arch/c6x/ needs <asm/asm-offsets.h> to build
since it contains _TIF_SIGNALfoobar #defines, so add it.
Placates these build errors:
../arch/c6x/kernel/signal.c: In function 'do_notify_resume':
../arch/c6x/kernel/signal.c:316:27: error: '_TIF_SIGPENDING' undeclared (first use in this function); did you mean 'TIF_SIGPENDING'?
316 | if (thread_info_flags & (_TIF_SIGPENDING | _TIF_NOTIFY_SIGNAL))
| ^~~~~~~~~~~~~~~
../arch/c6x/kernel/signal.c:316:27: note: each undeclared identifier is reported only once for each function it appears in
../arch/c6x/kernel/signal.c:316:45: error: '_TIF_NOTIFY_SIGNAL' undeclared (first use in this function); did you mean 'TIF_NOTIFY_SIGNAL'?
316 | if (thread_info_flags & (_TIF_SIGPENDING | _TIF_NOTIFY_SIGNAL))
| ^~~~~~~~~~~~~~~~~~
Fixes: b7560cfc3f8a ("c6x: add support for TIF_NOTIFY_SIGNAL")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-c6x-dev@linux-c6x.org
Cc: Jens Axboe <axboe@kernel.dk>
Cc: Mark Salter <msalter@redhat.com>
Cc: Aurelien Jacquiot <jacquiot.aurelien@gmail.com>
---
arch/c6x/kernel/signal.c | 1 +
1 file changed, 1 insertion(+)
--- linux-next-20201209.orig/arch/c6x/kernel/signal.c
+++ linux-next-20201209/arch/c6x/kernel/signal.c
@@ -13,6 +13,7 @@
#include <linux/syscalls.h>
#include <linux/tracehook.h>
+#include <asm/asm-offsets.h>
#include <asm/ucontext.h>
#include <asm/cacheflush.h>
next reply other threads:[~2020-12-10 3:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 3:17 Randy Dunlap [this message]
2020-12-12 16:17 ` Jens Axboe
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=20201210031742.14534-1-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=axboe@kernel.dk \
--cc=jacquiot.aurelien@gmail.com \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msalter@redhat.com \
/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®