All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: Dave Airlie <airlied@gmail.com>,
	DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: [git pull] drm/radeon: reset ring saving branch
Date: Tue, 17 Jul 2012 11:39:49 +0200	[thread overview]
Message-ID: <500532E5.8070202@vodafone.de> (raw)

Hi Dave,

I think it is easier if I just send you a pull request of my branch 
instead of individual patches.

So please pull the this branch into -next:
     git://people.freedesktop.org/~deathsimple/linux next

It contains the following changes:

Christian König (14):
       drm/radeon: add error handling to fence_wait_empty_locked
       drm/radeon: add error handling to radeon_vm_unbind_locked
       drm/radeon: fix fence related segfault in CS
       drm/radeon: fix ring commit padding
       drm/radeon: fix fence value access
       drm/radeon: fix fence init after resume
       drm/radeon: remove FIXME comment from chipset suspend
       drm/radeon: make cp init on cayman more robust
       drm/radeon: remove ip_pool start/suspend
       drm/radeon: remove r600_blit_suspend
       drm/radeon: remove vm_manager start/suspend
       drm/radeon: move radeon_ib_ring_tests out of chipset code
       drm/radeon: record what is next valid wptr for each ring v4
       drm/radeon: implement ring saving on reset v4

Jerome Glisse (1):
       drm/radeon: add an exclusive lock for GPU reset v2

All patches have been on the list for quite a while and contain the 
necessary Signed-off-by and Reviewed-by lines.

Cheers,
Christian.

             reply	other threads:[~2012-07-17  9:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-17  9:39 Christian König [this message]
2012-07-17  9:46 ` [git pull] drm/radeon: reset ring saving branch Dave Airlie
2012-07-17 10:04   ` Christian König
2012-07-17 10:14     ` Dave Airlie

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=500532E5.8070202@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=airlied@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.