All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oded Gabbay <oded.gabbay@amd.com>
To: airlied@gmail.com, dri-devel@lists.freedesktop.org
Cc: alexander.deucher@amd.com
Subject: [PULL] amdkfd-next-3.19
Date: Fri, 5 Dec 2014 22:05:26 +0200	[thread overview]
Message-ID: <20141205200526.GA32611@amd.com> (raw)

Hi Dave,

As discussed on irc, I'm sending a pull request with one important change:

- Disable support for 32-bit user processes. This is done due to AMD's decision
  to remove support for 32-bit user processes on Linux for its HSA stack.

Thanks,

Oded

The following changes since commit 7608867d0c4d9da30e9efe6a53ff4ee1e6c4990b:

  Merge tag 'drm-intel-next-fixes-2014-12-04' of git://anongit.freedesktop.org/drm-intel into drm-next (2014-12-05 11:11:57 +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 a18069c132cb0d065ff23c05977d06ea0c78404f:

  amdkfd: Disable support for 32-bit user processes (2014-12-05 22:01:35 +0200)

----------------------------------------------------------------
Oded Gabbay (1):
      amdkfd: Disable support for 32-bit user processes

 drivers/gpu/drm/amd/amdkfd/kfd_chardev.c | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2014-12-05 20:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 20:05 Oded Gabbay [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-11-26 20:40 [PULL] amdkfd-next-3.19 Oded Gabbay
2014-11-21 21:06 Oded Gabbay
2014-11-21 21:06 ` Oded Gabbay

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=20141205200526.GA32611@amd.com \
    --to=oded.gabbay@amd.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 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.