From: Lyude Paul <lyude@redhat.com>
To: amd-gfx@lists.freedesktop.org
Cc: "Pankaj Bharadiya" <pankaj.laxminarayan.bharadiya@intel.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Leo Li" <sunpeng.li@amd.com>,
"Mikita Lipski" <mikita.lipski@amd.com>,
"David Airlie" <airlied@linux.ie>,
"Christian König" <christian.koenig@amd.com>,
"David Francis" <david.francis@amd.com>,
linux-kernel@vger.kernel.org,
"Nicholas Kazlauskas" <nicholas.kazlauskas@amd.com>,
dri-devel@lists.freedesktop.org,
"David (ChunMing) Zhou" <david1.zhou@amd.com>,
"Harry Wentland" <harry.wentland@amd.com>,
"Wenjing Liu" <wenjing.liu@amd.com>,
"Lyude Paul" <lyude@redhat.com>,
"Rodrigo Siqueira" <rodrigo.siqueira@amd.com>,
"Anthony Koo" <anthony.koo@amd.com>,
"Wyatt Wood" <wyatt.wood@amd.com>, "Aric Cyr" <aric.cyr@amd.com>
Subject: [PATCH 0/2] drm/amdgpu: Remove duplicated DPCD logging
Date: Tue, 31 Mar 2020 17:22:22 -0400 [thread overview]
Message-ID: <20200331212228.139219-1-lyude@redhat.com> (raw)
There's a bunch of messy DPCD tracing code in amdgpu that isn't needed
since we already support this in DRM. Plus, it's really spammy. So, just
get rid of it.
Lyude Paul (2):
drm/amd/amdgpu_dm/mst: Remove useless sideband tracing
drm/amd/dc: Kill dc_conn_log_hex_linux()
.../display/amdgpu_dm/amdgpu_dm_mst_types.c | 43 -------------------
.../gpu/drm/amd/display/dc/basics/Makefile | 3 +-
.../drm/amd/display/dc/basics/log_helpers.c | 39 -----------------
.../amd/display/include/logger_interface.h | 4 --
4 files changed, 1 insertion(+), 88 deletions(-)
delete mode 100644 drivers/gpu/drm/amd/display/dc/basics/log_helpers.c
--
2.25.1
next reply other threads:[~2020-03-31 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 21:22 Lyude Paul [this message]
2020-03-31 21:22 ` [PATCH 1/2] drm/amd/amdgpu_dm/mst: Remove useless sideband tracing Lyude Paul
2020-03-31 21:22 ` [PATCH 2/2] drm/amd/dc: Kill dc_conn_log_hex_linux() Lyude Paul
2020-04-01 13:00 ` Kazlauskas, Nicholas
2020-04-01 18:18 ` Alex Deucher
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=20200331212228.139219-1-lyude@redhat.com \
--to=lyude@redhat.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=anthony.koo@amd.com \
--cc=aric.cyr@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=david.francis@amd.com \
--cc=david1.zhou@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikita.lipski@amd.com \
--cc=nicholas.kazlauskas@amd.com \
--cc=pankaj.laxminarayan.bharadiya@intel.com \
--cc=rodrigo.siqueira@amd.com \
--cc=sunpeng.li@amd.com \
--cc=wenjing.liu@amd.com \
--cc=wyatt.wood@amd.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®