From: yq882255@163.com
To: dri-devel@lists.freedesktop.org
Cc: "Erico Nunes" <nunes.erico@gmail.com>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
lima@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Qiang Yu" <yuq825@gmail.com>
Subject: [PATCH 0/3] Revert lima fdinfo patchset
Date: Tue, 4 Apr 2023 08:25:58 +0800 [thread overview]
Message-ID: <20230404002601.24136-1-yq882255@163.com> (raw)
From: Qiang Yu <yuq825@gmail.com>
Upstream has reverted the dependant commit
df622729ddbf ("drm/scheduler: track GPU active time per entity""),
but this patchset has been pushed to drm-misc-next which still
has that commit. To avoid other branch build fail after merge
drm-misc-next, just revert the lima patchset on drm-misc-next too.
Qiang Yu (3):
Revert "drm/lima: add show_fdinfo for drm usage stats"
Revert "drm/lima: allocate unique id per drm_file"
Revert "drm/lima: add usage counting method to ctx_mgr"
drivers/gpu/drm/lima/lima_ctx.c | 30 +--------------------
drivers/gpu/drm/lima/lima_ctx.h | 3 ---
drivers/gpu/drm/lima/lima_device.h | 3 ---
drivers/gpu/drm/lima/lima_drv.c | 43 +-----------------------------
drivers/gpu/drm/lima/lima_drv.h | 1 -
5 files changed, 2 insertions(+), 78 deletions(-)
--
2.25.1
next reply other threads:[~2023-04-04 0:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 0:25 yq882255 [this message]
2023-04-04 0:25 ` [PATCH 1/3] Revert "drm/lima: add show_fdinfo for drm usage stats" yq882255
2023-04-04 19:29 ` Daniel Vetter
2023-04-04 0:26 ` [PATCH 2/3] Revert "drm/lima: allocate unique id per drm_file" yq882255
2023-04-04 0:26 ` [PATCH 3/3] Revert "drm/lima: add usage counting method to ctx_mgr" yq882255
2023-04-04 15:17 ` [PATCH 0/3] Revert lima fdinfo patchset Emil Velikov
2023-04-04 19:28 ` Daniel Vetter
2023-04-05 0:50 ` Qiang Yu
2023-04-05 8:43 ` 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=20230404002601.24136-1-yq882255@163.com \
--to=yq882255@163.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=l.stach@pengutronix.de \
--cc=lima@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nunes.erico@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=ville.syrjala@linux.intel.com \
--cc=yuq825@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
all inboxes | Powered by JetHome®