dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Witten <mfwitten@gmail.com>
To: David Airlie <airlied@linux.ie>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/7] DRM/Radeon Cleanup
Date: Mon, 26 Sep 2011 20:47:10 -0000	[thread overview]
Message-ID: <0fe01c9fdc43414da59dfc11820d8873-mfwitten@gmail.com> (raw)
In-Reply-To: <b9878116a1944723846034345928f0a8-mfwitten@gmail.com>

On Wed, 21 Sep 2011 22:50:57 -0000, Michael Witten wrote:

> Whilst working on my failing Radeon GPU:
>
>   Subject: Re: Curious experiences with a Radeon on the fritz
>   Date: Wed, 21 Sep 2011 18:52:19 -0000
>   Message-ID: <c0efd8527ff34853a23f1d706be29c67-mfwitten@gmail.com>
>   http://lists.freedesktop.org/archives/dri-devel/2011-September/014506.html
>
> I made the following trivial improvements to the DRM/Radeon code
> along the way ([6] fixes a bug):
>
>   [1] DRM: comment: drm_crtc{=>_helper}_set_mode
>   [2] DRM: comment: halve -> half
>   [3] DRM: cleanup: Remove unused `gamma_size'
>   [4] DRM: comment: gdm_proc_lists -> drm_proc_lists
>   [5] DRM: cleanup: `size == 0' is never true
>   [6] DRM: bug: RADEON_DEBUGFS_MAX_{NUM_FILES => COMPONENTS}
>   [7] DRM: cleanup: Remove unsused `tmp'
>
> Here is the overall difference:
>
>  drivers/gpu/drm/drm_crtc_helper.c       |    2 +-
>  drivers/gpu/drm/drm_fb_helper.c         |    3 ---
>  drivers/gpu/drm/drm_irq.c               |    4 ++--
>  drivers/gpu/drm/drm_proc.c              |    2 +-
>  drivers/gpu/drm/radeon/radeon.h         |    2 +-
>  drivers/gpu/drm/radeon/radeon_bios.c    |    2 +-
>  drivers/gpu/drm/radeon/radeon_combios.c |    2 +-
>  drivers/gpu/drm/radeon/radeon_device.c  |   13 ++++++++-----
>  8 files changed, 15 insertions(+), 15 deletions(-)

When you get the chance, David, please apply all but [4] and [7].

  * Patch [4] is not really helpful, because it poorly changes a
    comment in what is deprecated, probably erroneous code anyway.

  * [7] was a mistake on my part.

  parent reply	other threads:[~2011-09-26 20:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 22:50 [PATCH 0/7] DRM/Radeon Cleanup Michael Witten
2011-09-21 22:49 ` [PATCH 1/7] DRM: comment: drm_crtc{=>_helper}_set_mode Michael Witten
2011-09-21 22:50 ` [PATCH 2/7] DRM: comment: halve -> half Michael Witten
2011-09-21 22:50 ` [PATCH 3/7] DRM: cleanup: Remove unused `gamma_size' Michael Witten
2011-09-21 22:50 ` [PATCH 5/7] DRM: cleanup: `size == 0' is never true Michael Witten
2011-09-21 22:50 ` [PATCH 6/7] DRM: bug: RADEON_DEBUGFS_MAX_{NUM_FILES => COMPONENTS} Michael Witten
2011-09-21 22:50 ` [PATCH 4/7] DRM: comment: gdm_proc_lists -> drm_proc_lists Michael Witten
2011-09-21 22:50 ` [PATCH 7/7] DRM: cleanup: Remove unsused `tmp' Michael Witten
2011-09-22  9:24   ` Michel Dänzer
2011-09-22 17:16     ` Michael Witten
2015-04-14 13:44   ` [PATCH] trivial: Remove unused variable `tmp' from `radeon_combios_get_lvds_info()' Michael Witten
2015-04-14 15:54     ` Michael Witten
2011-09-26 20:47 ` Michael Witten [this message]
2011-10-07 19:20   ` [PATCH] DRM: bug: RADEON_DEBUGFS_MAX_{NUM_FILES => COMPONENTS} Michael Witten
2011-10-24 23:21     ` Michael Witten
2011-10-25  1:35       ` Ilija Hadzic
2011-10-26 15:07         ` Michael Witten

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=0fe01c9fdc43414da59dfc11820d8873-mfwitten@gmail.com \
    --to=mfwitten@gmail.com \
    --cc=airlied@linux.ie \
    --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