All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oded Gabbay <oded.gabbay@amd.com>
To: David Airlie <airlied@linux.ie>, dri-devel@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>
Subject: [PULL] amdkfd-next-3.19-fixes
Date: Thu, 4 Dec 2014 16:41:24 +0200	[thread overview]
Message-ID: <20141204144124.GA14939@amd.com> (raw)

Hi Dave,

Just three more fixes for 3.19. 
This is the last request until -rc1. I will have our QA team run a full
HSA stack test on 3.19-rc1 and if we find problems, I will send a fixes pull
request.

- Oded

The following changes since commit d5b75dc01fa9c699aee5f82f5dbe508da438ff94:

  Merge branch 'vmwgfx-next' of git://people.freedesktop.org/~thomash/linux into drm-next (2014-12-03 19:35:05 +1000)

are available in the git repository at:


  git://people.freedesktop.org/~gabbayo/linux amdkfd-next-3.19

for you to fetch changes up to a550bb3d5313c3d894cac552e13037394ac78fd4:

  amdkfd: Set *buffer_ptr to NULL in case of error (2014-12-04 14:09:02 +0200)

----------------------------------------------------------------
Oded Gabbay (1):
      amdkfd: Set *buffer_ptr to NULL in case of error

Sasha Levin (2):
      amdkfd: use sizeof(long) granularity for the pasid bitmask
      amdkfd: use atomic allocations within srcu callbacks

 drivers/gpu/drm/amd/amdkfd/kfd_kernel_queue.c | 8 +++++++-
 drivers/gpu/drm/amd/amdkfd/kfd_pasid.c        | 3 +--
 drivers/gpu/drm/amd/amdkfd/kfd_process.c      | 2 +-
 3 files changed, 9 insertions(+), 4 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

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

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20141204144124.GA14939@amd.com \
    --to=oded.gabbay@amd.com \
    --cc=airlied@linux.ie \
    --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 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.