dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: dri-devel@lists.freedesktop.org, airlied@gmail.com
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: [pull] radeon drm-next-3.19
Date: Fri, 12 Dec 2014 09:34:17 -0500	[thread overview]
Message-ID: <1418394857-21322-1-git-send-email-alexander.deucher@amd.com> (raw)

Hi Dave,

Just three small bug fixes for 3.19

The following changes since commit b59f78228ca3d81ecb491fb17d348b07002dbe03:

  Merge tag 'drm-intel-next-fixes-2014-12-11' of git://anongit.freedesktop.org/drm-intel into drm-next (2014-12-12 11:39:49 +1000)

are available in the git repository at:


  git://people.freedesktop.org/~agd5f/linux drm-next-3.19

for you to fetch changes up to ac609761ad39b8a12c0601f0a3f7bec42004c9aa:

  drm/radeon: properly filter DP1.2 4k modes on non-DP1.2 hw (2014-12-12 09:25:29 -0500)

----------------------------------------------------------------
Alex Deucher (3):
      drm/radeon: KV has three PPLLs (v2)
      drm/radeon: fix sad_count check for dce3
      drm/radeon: properly filter DP1.2 4k modes on non-DP1.2 hw

 drivers/gpu/drm/radeon/atombios_crtc.c | 8 ++++----
 drivers/gpu/drm/radeon/atombios_dp.c   | 4 ++++
 drivers/gpu/drm/radeon/dce3_1_afmt.c   | 2 +-
 3 files changed, 9 insertions(+), 5 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-12-12 14:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12 14:34 Alex Deucher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-12-04 21:40 [pull] radeon drm-next-3.19 Alex Deucher
2014-11-20 18:22 Alex Deucher
2014-11-12 21:46 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=1418394857-21322-1-git-send-email-alexander.deucher@amd.com \
    --to=alexdeucher@gmail.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@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