From: "Kristian H. Kristensen" <hoegsberg@google.com>
To: dri-devel@lists.freedesktop.org, Gerd Hoffmann <kraxel@redhat.com>
Cc: "Kristian H. Kristensen" <hoegsberg@google.com>
Subject: [PATCH] udmabuf: Add missing compact_ioctl
Date: Thu, 3 Sep 2020 18:16:52 +0000 [thread overview]
Message-ID: <20200903181652.432067-1-hoegsberg@google.com> (raw)
Make sure we can use this on mixed systems.
Signed-off-by: Kristian H. Kristensen <hoegsberg@google.com>
---
drivers/dma-buf/udmabuf.c | 3 +++
1 file changed, 3 insertions(+)
Sorry Gerd for all the spam. Once I finally got git send-email
working, I ended up sending a version with all ChromeOS decorations,
of course. Here's a normal upstream version.
Email based workflow - the barrier is real.
Kristian
diff --git a/drivers/dma-buf/udmabuf.c b/drivers/dma-buf/udmabuf.c
index 9635897458a0..6f4ff6ede050 100644
--- a/drivers/dma-buf/udmabuf.c
+++ b/drivers/dma-buf/udmabuf.c
@@ -270,6 +270,9 @@ static long udmabuf_ioctl(struct file *filp, unsigned int ioctl,
static const struct file_operations udmabuf_fops = {
.owner = THIS_MODULE,
.unlocked_ioctl = udmabuf_ioctl,
+#ifdef CONFIG_COMPAT
+ .compat_ioctl = udmabuf_ioctl,
+#endif
};
static struct miscdevice udmabuf_misc = {
--
2.28.0.402.g5ffc5be6b7-goog
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-09-03 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 18:16 Kristian H. Kristensen [this message]
2020-09-07 5:31 ` [PATCH] udmabuf: Add missing compact_ioctl Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2020-09-04 18:38 Kristian H. Kristensen
2020-09-03 7:18 Kristian H. Kristensen
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=20200903181652.432067-1-hoegsberg@google.com \
--to=hoegsberg@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kraxel@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