dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Oded Gabbay <oded.gabbay@gmail.com>
To: David Airlie <airlied@linux.ie>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PULL] drm-amdkfd-next
Date: Tue, 27 Sep 2016 09:55:45 +0300	[thread overview]
Message-ID: <CAFCwf13+X_KT=bM3OQ=n4zYuCu8EW-syzkcp-Ss3dgUPSeituA@mail.gmail.com> (raw)
In-Reply-To: <20160919194923.GA24335@gmail.com>

Hi Dave,
Just wanted to make sure this pull request hasn't got lost in the mail.

Thanks,
      Oded

On Mon, Sep 19, 2016 at 10:49 PM, Oded Gabbay <oded.gabbay@gmail.com> wrote:
> Hi Dave,
>
> This is amdkfd's pull request for kernel 4.9. It contains a fix to a possible
> infinite loop bug and a couple of other minor "cleaning" patches.
>
> Thanks,
>     Oded
>
> The following changes since commit 9f8cf165c62913244479832f04c44cd77ffc9293:
>
>   Merge tag 'topic/drm-misc-2016-09-19' of git://anongit.freedesktop.org/drm-intel into drm-next (2016-09-19 17:16:02 +1000)
>
> are available in the git repository at:
>
>   git://people.freedesktop.org/~gabbayo/linux tags/drm-amdkfd-next-2016-09-19
>
> for you to fetch changes up to e88a614c403573e861f82c063d8aee25cf109f17:
>
>   drm/amdkfd: Pass 'struct queue_propertices' by reference (2016-09-19 20:58:35 +0300)
>
> ----------------------------------------------------------------
> Edward O'Callaghan (6):
>       drm/amdkfd: Tidy up kfd_generate_gpu_id() uint64_t bitshift unpack
>       drm/amdkfd: Add some missing memset zero'ing in queue init func
>       drm/amdkfd: Reuse function to find a process through pasid
>       drm/amdkfd: Fix possible infinite loop
>       drm/amdkfd: Unify multiple calls to pr_debug() into one
>       drm/amdkfd: Pass 'struct queue_propertices' by reference
>
>  drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v7.c  | 17 +++---
>  drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v8.c  | 17 +++---
>  drivers/gpu/drm/amd/amdkfd/kfd_doorbell.c          | 16 +++---
>  drivers/gpu/drm/amd/amdkfd/kfd_kernel_queue.c      |  5 +-
>  drivers/gpu/drm/amd/amdkfd/kfd_priv.h              |  2 +-
>  drivers/gpu/drm/amd/amdkfd/kfd_process.c           | 61 +++++++++-------------
>  .../gpu/drm/amd/amdkfd/kfd_process_queue_manager.c |  2 +-
>  drivers/gpu/drm/amd/amdkfd/kfd_queue.c             |  4 +-
>  drivers/gpu/drm/amd/amdkfd/kfd_topology.c          |  8 +--
>  9 files changed, 65 insertions(+), 67 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-09-27  6:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19 19:49 [PULL] drm-amdkfd-next Oded Gabbay
2016-09-27  6:55 ` Oded Gabbay [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-01-16 15:39 Oded Gabbay
2016-07-03  5:14 Oded Gabbay
2016-05-04  6:31 Oded Gabbay
2016-02-27 21:07 Oded Gabbay
2015-07-20  8:01 Oded Gabbay
2015-06-01  5:53 Oded Gabbay
2015-05-18  6:29 Oded Gabbay
2015-05-18  6:31 ` Oded Gabbay
2015-05-19  0:16   ` Dave Airlie
2015-05-19  4:39     ` Oded Gabbay
2015-03-25 12:22 Oded Gabbay
2015-01-21 12:38 Oded Gabbay
2015-01-21 23:47 ` Dave Airlie
2015-01-22  9:42   ` Oded Gabbay
2015-01-09 20:33 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='CAFCwf13+X_KT=bM3OQ=n4zYuCu8EW-syzkcp-Ss3dgUPSeituA@mail.gmail.com' \
    --to=oded.gabbay@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;
as well as URLs for NNTP newsgroup(s).