Attachment 17328 Details for Bug 16474 – Add shmem_getpage declaration to make i915-gem part build

[patch] Add shmem_getpage declaration to make i915-gem part build

0001-include-shmem_getpage-declaration.patch (text/plain), 1.35 KB, created by Johannes Engel on 2008-06-23 07:54:59 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Johannes Engel

Created: 2008-06-23 07:54:59 UTC

Size: 1.35 KB

patch

obsolete

>From 626b9cdd166b3e872c84492f57c1ba131e53ff2b Mon Sep 17 00:00:00 2001
>From: Johannes Engel <engel@wmaz5.math.uni-wuppertal.de>
>Date: Mon, 23 Jun 2008 15:52:02 +0100
>Subject: [PATCH 1/1] include shmem_getpage declaration
>
>Signed-off-by: Johannes Engel <engel@wmaz5.math.uni-wuppertal.de>
>---
> linux-core/i915_gem.c |    1 +
> linux-core/i915_gem.h |    9 +++++++++
> 2 files changed, 10 insertions(+), 0 deletions(-)
> create mode 100644 linux-core/i915_gem.h
>
>diff --git a/linux-core/i915_gem.c b/linux-core/i915_gem.c
>index 4361b06..d814bc1 100644
>--- a/linux-core/i915_gem.c
>+++ b/linux-core/i915_gem.c
>@@ -29,6 +29,7 @@
> #include "drm.h"
> #include "i915_drm.h"
> #include "i915_drv.h"
>+#include "i915_gem.h"
> 
> #define WATCH_COHERENCY	0
> #define WATCH_BUF	0
>diff --git a/linux-core/i915_gem.h b/linux-core/i915_gem.h
>new file mode 100644
>index 0000000..5481841
>--- /dev/null
>+++ b/linux-core/i915_gem.h
>@@ -0,0 +1,9 @@
>+enum sgp_type {
>+        SGP_READ,       /* don't exceed i_size, don't allocate page */
>+        SGP_CACHE,      /* don't exceed i_size, may allocate page */
>+        SGP_DIRTY,      /* like SGP_CACHE, but set new page dirty */
>+        SGP_WRITE,      /* may exceed i_size, may allocate page */
>+};
>+
>+extern int shmem_getpage(struct inode *inode, unsigned long idx,
>+                        struct page **pagep, enum sgp_type sgp, int *type);
>-- 
>1.5.4.5
>

Actions: View | Splinter Review

Attachments on bug 16474: 17328 | 17329 | 18005

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.