From: "Maxime Ripard" <mripard@kernel.org>
To: "Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>
Cc: dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
linux-arm-msm@vger.kernel.org,
"Abhinav Kumar" <quic_abhinavk@quicinc.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"David Airlie" <airlied@gmail.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Rob Clark" <robdclark@gmail.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>
Subject: Re: [PATCH RESEND 1/5] drm/atomic: add private obj state to state dump
Date: Mon, 04 Dec 2023 08:49:52 +0000 [thread overview]
Message-ID: <335240cdb8b6b980c2380bdc25fb2833.mripard@kernel.org> (raw)
In-Reply-To: <20231203000532.1290480-2-dmitry.baryshkov@linaro.org>
On Sun, 3 Dec 2023 03:05:28 +0300, Dmitry Baryshkov wrote:
> The drm_atomic_print_new_state() already prints private object state via
> drm_atomic_private_obj_print_state(). Add private object state dumping
> to __drm_state_dump(), so that it is also included into drm_state_dump()
> output and into debugfs/dri/N/state file.
>
>
> [ ... ]
Acked-by: Maxime Ripard <mripard@kernel.org>
Thanks!
Maxime
next prev parent reply other threads:[~2023-12-04 8:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 0:05 [PATCH RESEND 0/5] drm/msm: cleanup private obj handling Dmitry Baryshkov
2023-12-03 0:05 ` [PATCH RESEND 1/5] drm/atomic: add private obj state to state dump Dmitry Baryshkov
2023-12-04 8:49 ` Maxime Ripard [this message]
2023-12-03 0:05 ` [PATCH RESEND 2/5] drm/msm/dpu: finalise global state object Dmitry Baryshkov
2024-02-09 19:57 ` Abhinav Kumar
2023-12-03 0:05 ` [PATCH RESEND 3/5] drm/msm/dpu: drop global_state_lock Dmitry Baryshkov
2024-02-09 22:28 ` Abhinav Kumar
2023-12-03 0:05 ` [PATCH RESEND 4/5] drm/msm/mdp5: migrate SMP dumping to using atomic_print_state Dmitry Baryshkov
2024-02-09 22:34 ` Abhinav Kumar
2023-12-03 0:05 ` [PATCH RESEND 5/5] drm/msm/mdp5: drop global_state_lock Dmitry Baryshkov
2024-02-09 23:01 ` Abhinav Kumar
2024-02-19 12:30 ` [PATCH RESEND 0/5] drm/msm: cleanup private obj handling Dmitry Baryshkov
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=335240cdb8b6b980c2380bdc25fb2833.mripard@kernel.org \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=tzimmermann@suse.de \
/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