From: Ramalingam C <ramalingam.c@intel.com>
To: igt-dev <igt-dev@lists.freedesktop.org>,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: [igt-dev] [PATCH i-g-t v3 2/2] lib/kmstest_dumb_map_buffer: docs update
Date: Fri, 29 Nov 2019 16:54:12 +0530 [thread overview]
Message-ID: <20191129112412.8263-2-ramalingam.c@intel.com> (raw)
In-Reply-To: <20191129112412.8263-1-ramalingam.c@intel.com>
Added the need for munmapping the returned pointer, after its usage.
Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
---
lib/igt_kms.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/igt_kms.c b/lib/igt_kms.c
index e9b80b9bcb81..9242065ed36a 100644
--- a/lib/igt_kms.c
+++ b/lib/igt_kms.c
@@ -837,6 +837,7 @@ uint32_t kmstest_dumb_create(int fd, int width, int height, int bpp,
* @size: Length of the mapping, must be greater than 0
* @prot: Describes the memory protection of the mapping
* Returns: A pointer representing the start of the virtual mapping
+ * Caller of this function should munmap the pointer returned, after its usage.
*/
void *kmstest_dumb_map_buffer(int fd, uint32_t handle, uint64_t size,
unsigned prot)
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-11-29 11:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 11:24 [igt-dev] [PATCH i-g-t v3 1/2] tests/dumb_buffer: Tests for creation and map Ramalingam C
2019-11-29 11:24 ` Ramalingam C [this message]
2019-11-29 11:37 ` [igt-dev] ✗ GitLab.Pipeline: warning for series starting with [i-g-t,v3,1/2] " Patchwork
2019-11-29 11:53 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-11-28 18:09 [igt-dev] [PATCH i-g-t v3 1/2] " Ramalingam C
2019-11-28 18:09 ` [igt-dev] [PATCH i-g-t v3 2/2] lib/kmstest_dumb_map_buffer: docs update Ramalingam C
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=20191129112412.8263-2-ramalingam.c@intel.com \
--to=ramalingam.c@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox