From: Rhys Kidd <rhyskidd@gmail.com>
To: intel-gfx@lists.freedesktop.org
Cc: Ben Widawsky <ben@bwidawsk.net>
Subject: [PATCH i-g-t 3/3] debugger: No longer rely on compatability define in intel_bufmgr.h
Date: Tue, 9 Jan 2018 23:25:11 -0500 [thread overview]
Message-ID: <20180110042511.7551-3-rhyskidd@gmail.com> (raw)
In-Reply-To: <20180110042511.7551-1-rhyskidd@gmail.com>
Symbol rename from dri_* to drm_intel_* introduced a number of
compatability defines within intel_bufmgr.h.
Replace the old function with the new function, consistent with
the balance of this file.
Signed-off-by: Rhys Kidd <rhyskidd@gmail.com>
---
debugger/eudb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debugger/eudb.c b/debugger/eudb.c
index 8384950a..de37be52 100644
--- a/debugger/eudb.c
+++ b/debugger/eudb.c
@@ -562,7 +562,7 @@ int main(int argc, char* argv[]) {
if (fscanf(stdin, "%1d", &dh_handle) == 0)
exit(1);
}
- scratch_bo = intel_bo_gem_create_from_name(bufmgr, "scratch", dh_handle);
+ scratch_bo = drm_intel_bo_gem_create_from_name(bufmgr, "scratch", dh_handle);
if (scratch_bo == NULL) {
fprintf(stderr, "Couldn't flink buffer\n");
abort();
--
2.14.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-01-10 4:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 4:25 [PATCH i-g-t 1/3] debugger: Convert to current intel_register_access_init() Rhys Kidd
2018-01-10 4:25 ` [PATCH i-g-t 2/3] debugger: Clean up register access helper in debug_rdata Rhys Kidd
2018-01-10 4:25 ` Rhys Kidd [this message]
2018-01-16 16:29 ` [PATCH i-g-t 3/3] debugger: No longer rely on compatability define in intel_bufmgr.h Ben Widawsky
2018-01-10 5:00 ` ✓ Fi.CI.BAT: success for series starting with [1/3] debugger: Convert to current intel_register_access_init() Patchwork
2018-01-10 6:48 ` ✗ Fi.CI.IGT: failure " Patchwork
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=20180110042511.7551-3-rhyskidd@gmail.com \
--to=rhyskidd@gmail.com \
--cc=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
/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.