From: Lukas Wunner <lukas@wunner.de>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>
Cc: Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk>
Subject: [PATCH RFC 5/5] gpu/doc: Convert to markdown harder
Date: Mon, 12 Oct 2015 09:10:33 +0200 [thread overview]
Message-ID: <e67c10e5e36991b4a646fda04a627ef14f1509d3.1444655697.git.lukas@wunner.de> (raw)
In-Reply-To: <cover.1444655697.git.lukas@wunner.de>
This snippet...
* Lock VMA manager for extended lookups. Only *_locked() VMA function calls
* are allowed while holding this lock. All other contexts are blocked from VMA
* until the lock is released via drm_vma_offset_unlock_lookup().
...causes markdown-enabled kernel-doc to barf:
debian/build/build-doc/Documentation/DocBook/gpu.aux.xml:3247: parser error : Opening and ending tag mismatch: emphasis line 3247 and function
*<function><emphasis>locked</function> VMA function calls are allowed while
^
/root/airlied/debian/build/build-doc/Documentation/DocBook/gpu.aux.xml:3249: parser error : Opening and ending tag mismatch: function line 3249 and emphasis
released via <function>drm</emphasis>vma_offset_unlock_lookup</function>.
^
unable to parse /root/airlied/debian/build/build-doc/Documentation/DocBook/gpu.aux.xml
A quick workaround is to replace *_locked() by X_locked().
Cc: Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk>
Signed-off-by: Lukas Wunner <lukas@wunner.de>
---
include/drm/drm_vma_manager.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/drm/drm_vma_manager.h b/include/drm/drm_vma_manager.h
index 2ca44db..c1e41b8 100644
--- a/include/drm/drm_vma_manager.h
+++ b/include/drm/drm_vma_manager.h
@@ -97,7 +97,7 @@ drm_vma_offset_exact_lookup(struct drm_vma_offset_manager *mgr,
* drm_vma_offset_lock_lookup() - Lock lookup for extended private use
* @mgr: Manager object
*
- * Lock VMA manager for extended lookups. Only *_locked() VMA function calls
+ * Lock VMA manager for extended lookups. Only X_locked() VMA function calls
* are allowed while holding this lock. All other contexts are blocked from VMA
* until the lock is released via drm_vma_offset_unlock_lookup().
*
--
1.8.5.2 (Apple Git-48)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-10-12 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 7:55 [PATCH] [RFC] drm/doc: Rename docbook to gpu.tmpl Daniel Vetter
2015-10-07 14:02 ` Jani Nikula
2015-10-12 13:14 ` [PATCH RFC 0/5] " Lukas Wunner
2015-10-07 7:55 ` [PATCH RFC 2/5] " Lukas Wunner
2015-10-10 8:22 ` [PATCH RFC 1/5] drm/doc: Remove TODO about drm_vblank_pre/post_modeset() Lukas Wunner
2015-10-11 9:26 ` [PATCH RFC 3/5] gpu/doc: Fix up remaining occurrences of old document title Lukas Wunner
2015-10-11 9:55 ` [PATCH RFC 4/5] gpu/doc: Add vga_switcheroo documentation Lukas Wunner
2015-10-12 7:10 ` Lukas Wunner [this message]
2015-10-14 13:59 ` [PATCH RFC 5/5] gpu/doc: Convert to markdown harder Daniel Vetter
2015-10-14 14:04 ` Danilo Cesar Lemes de Paula
2015-10-14 15:54 ` Lukas Wunner
2015-10-14 17:03 ` Daniel Vetter
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=e67c10e5e36991b4a646fda04a627ef14f1509d3.1444655697.git.lukas@wunner.de \
--to=lukas@wunner.de \
--cc=daniel.vetter@ffwll.ch \
--cc=danilo.cesar@collabora.co.uk \
--cc=dri-devel@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.