From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH libdrm 4/4] modetest: print more about our properties
Date: Thu, 3 May 2012 13:33:07 +0200 [thread overview]
Message-ID: <20120503113255.GF4983@phenom.ffwll.local> (raw)
In-Reply-To: <1335041513-2486-4-git-send-email-przanoni@gmail.com>
On Sat, Apr 21, 2012 at 05:51:53PM -0300, Paulo Zanoni wrote:
> From: Paulo Zanoni <paulo.r.zanoni@intel.com>
>
> In the future we'll have more than just connector properties, so create
> a dump_prop function that can handle any property (instead of the
> current dump_props function that only handles connector properties).
>
> Also, make this function print a lot more information about the existing
> properties.
>
> Also change the printed indentation of the modes to make the output more
> readable.
>
> The previous function dump_props also segfaulted when we didn't have
> enought permissions. The new function does not segfault in this case (by
> checking for the return value of drmModeGetProperty).
>
> Reviewed-by: Eugeni Dodonov <eugeni.dodonov@intel.com>
> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Looks like this series here has been lost a bit. I've pushed all 4
patches, thanks.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
prev parent reply other threads:[~2012-05-03 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 20:51 [PATCH libdrm 1/4] modetest: fix some compiler warnings Paulo Zanoni
2012-04-21 20:51 ` [PATCH libdrm 2/4] modetest: fix drmModeGetConnector memory leak Paulo Zanoni
2012-04-21 20:51 ` [PATCH libdrm 3/4] modetest: call drmModeFreePlaneResources Paulo Zanoni
2012-04-21 20:51 ` [PATCH libdrm 4/4] modetest: print more about our properties Paulo Zanoni
2012-05-03 11:33 ` Daniel Vetter [this message]
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=20120503113255.GF4983@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=przanoni@gmail.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