From: Sultan Alsawaf <sultan@kerneltoast.com>
To: unlisted-recipients:; (no To-header on input)
Cc: sultan@kerneltoast.com, linux-kernel@vger.kernel.org,
linux-rt-users@vger.kernel.org, sebastian@breakpoint.cc,
tglx@linutronix.de, rostedt@goodmis.org
Subject: [PATCH] rt-tests: backfire: Don't include asm/uaccess.h directly
Date: Tue, 3 Sep 2019 12:13:21 -0700 [thread overview]
Message-ID: <20190903191321.6762-1-sultan@kerneltoast.com> (raw)
From: Sultan Alsawaf <sultan@kerneltoast.com>
Architecture-specific uaccess.h headers can have dependencies on
linux/uaccess.h (i.e., VERIFY_WRITE), so it cannot be included directly.
Since linux/uaccess.h includes asm/uaccess.h, just do that instead.
This fixes compile errors with certain kernels and architectures.
Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
---
src/backfire/backfire.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/backfire/backfire.c b/src/backfire/backfire.c
index aaf9c4a..a8ac9f5 100644
--- a/src/backfire/backfire.c
+++ b/src/backfire/backfire.c
@@ -30,8 +30,8 @@
#include <linux/miscdevice.h>
#include <linux/proc_fs.h>
#include <linux/spinlock.h>
+#include <linux/uaccess.h>
-#include <asm/uaccess.h>
#include <asm/system.h>
#define BACKFIRE_MINOR MISC_DYNAMIC_MINOR
--
2.23.0
next reply other threads:[~2019-09-03 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 19:13 Sultan Alsawaf [this message]
2019-09-16 21:57 ` [PATCH] rt-tests: backfire: Don't include asm/uaccess.h directly John Kacur
2019-09-17 7:15 ` Sultan Alsawaf
2019-09-17 10:28 ` Kurt Kanzenbach
2019-09-17 14:14 ` John Kacur
2019-09-17 10:24 ` Sebastian Andrzej Siewior
2019-09-17 14:12 ` John Kacur
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=20190903191321.6762-1-sultan@kerneltoast.com \
--to=sultan@kerneltoast.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sebastian@breakpoint.cc \
--cc=tglx@linutronix.de \
/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.