From: Michele Curti <michele.curti@gmail.com>
To: alexander.deucher@amd.com, christian.koenig@amd.com
Cc: Michele Curti <michele.curti@gmail.com>, dri-devel@lists.freedesktop.org
Subject: [PATCH 0/2] radeon/drm: dpm cleanups
Date: Tue, 14 Oct 2014 18:25:08 +0200 [thread overview]
Message-ID: <1413303910-1935-1-git-send-email-michele.curti@gmail.com> (raw)
Hi,
the first patch reduces the sparse warnings and the second removes unused
code. I think the patches could be applied independently but both act on
the dpm files, so here's why the series.
I'm not sure about the patches but at least I experiment with
git send-email..
Please don't kill me if you can :p
Michele
Michele Curti (2):
drm/radeon: reduce sparse false positive warnings
drm/radeon: remove never called dpm functions
drivers/gpu/drm/radeon/btc_dpm.c | 9 +-------
drivers/gpu/drm/radeon/ci_dpm.c | 40 +-----------------------------------
drivers/gpu/drm/radeon/cypress_dpm.c | 7 +------
drivers/gpu/drm/radeon/kv_dpm.c | 21 -------------------
drivers/gpu/drm/radeon/ni_dpm.c | 7 +------
drivers/gpu/drm/radeon/r600_dpm.c | 1 +
drivers/gpu/drm/radeon/rs780_dpm.c | 1 +
drivers/gpu/drm/radeon/rv6xx_dpm.c | 1 +
drivers/gpu/drm/radeon/rv770_dpm.c | 14 +------------
drivers/gpu/drm/radeon/si_dpm.c | 15 +-------------
drivers/gpu/drm/radeon/sumo_dpm.c | 13 +-----------
drivers/gpu/drm/radeon/trinity_dpm.c | 17 +--------------
12 files changed, 11 insertions(+), 135 deletions(-)
--
2.1.2
next reply other threads:[~2014-10-14 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 16:25 Michele Curti [this message]
2014-10-14 16:25 ` [PATCH 1/2] drm/radeon: reduce sparse false positive warnings Michele Curti
2014-10-16 14:34 ` Alex Deucher
2014-10-14 16:25 ` [PATCH 2/2] drm/radeon: remove never called dpm functions Michele Curti
2014-10-16 14:34 ` 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=1413303910-1935-1-git-send-email-michele.curti@gmail.com \
--to=michele.curti@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
/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