From: Alyssa Rosenzweig <alyssa@rosenzweig.io>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: dri-devel@lists.freedesktop.org,
Steven Price <steven.price@arm.com>,
Rob Herring <robh+dt@kernel.org>,
kernel@collabora.com, Emil Velikov <emil.velikov@collabora.com>
Subject: Re: [PATCH v3 0/4] drm/panfrost: Expose perf counters to userspace
Date: Wed, 29 May 2019 08:16:19 -0700 [thread overview]
Message-ID: <20190529151619.GC32127@rosenzweig.io> (raw)
In-Reply-To: <20190529095233.26277-1-boris.brezillon@collabora.com>
Woohoo! Patches 1-3 are R-b; patch 4 is A-b. Exciting progress! Hoping
to hear what Rob and Steven think :)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-29 15:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 9:52 [PATCH v3 0/4] drm/panfrost: Expose perf counters to userspace Boris Brezillon
2019-05-29 9:52 ` [PATCH v3 1/4] drm/panfrost: Move gpu_{write, read}() macros to panfrost_regs.h Boris Brezillon
2019-05-29 9:52 ` [PATCH v3 2/4] drm/panfrost: Add a module parameter to expose unstable ioctls Boris Brezillon
2019-06-10 14:08 ` Rob Herring
2019-05-29 9:52 ` [PATCH v3 3/4] drm/panfrost: Add an helper to check the GPU generation Boris Brezillon
2019-05-29 9:52 ` [PATCH v3 4/4] drm/panfrost: Expose performance counters through unstable ioctls Boris Brezillon
2019-05-30 22:45 ` kbuild test robot
2019-05-29 15:16 ` Alyssa Rosenzweig [this message]
2019-06-14 15:12 ` [PATCH v3 0/4] drm/panfrost: Expose perf counters to userspace Rob Herring
2019-06-14 16:23 ` Boris Brezillon
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=20190529151619.GC32127@rosenzweig.io \
--to=alyssa@rosenzweig.io \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=emil.velikov@collabora.com \
--cc=kernel@collabora.com \
--cc=robh+dt@kernel.org \
--cc=steven.price@arm.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