dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Oded Gabbay <oded.gabbay@gmail.com>
To: airlied@linux.ie
Cc: dri-devel@lists.freedesktop.org
Subject: [PULL] drm-amdkfd-next-fixes
Date: Sun, 30 Aug 2015 12:47:35 +0300	[thread overview]
Message-ID: <20150830094735.GA14904@odedg-home.redhat.com> (raw)

Hi Dave,

Just one small fix before 4.3 merge window:

- Use linux/mman.h instead of uapi's mman-common.h inside the driver.

Thanks,

    Oded

The following changes since commit 92cffd56b21c825579f3b37bc7803e4c37073076:

  drm/nouveau/dispnv04: fix build on powerpc (2015-08-28 20:33:58 +1000)

are available in the git repository at:

  git://people.freedesktop.org/~gabbayo/linux tags/drm-amdkfd-next-fixes-2015-08-30

for you to fetch changes up to 2497ee721524be80a7690dac0956d04c0ee954f0:

  amdkfd: use <linux/mman.h> instead of <uapi/asm-generic/mman-common.h> (2015-08-30 12:36:58 +0300)

----------------------------------------------------------------
Christoph Hellwig (1):
      amdkfd: use <linux/mman.h> instead of <uapi/asm-generic/mman-common.h>

 drivers/gpu/drm/amd/amdkfd/kfd_chardev.c     | 2 +-
 drivers/gpu/drm/amd/amdkfd/kfd_flat_memory.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2015-08-30  9:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-30  9:47 Oded Gabbay [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-03-15 12:13 [PULL] drm-amdkfd-next-fixes Oded Gabbay
2015-08-05  7:05 Oded Gabbay
2015-08-05  7:48 ` Daniel Vetter
2015-08-05  7:49   ` Oded Gabbay
2015-08-05  9:32     ` Daniel Vetter
2015-06-10 12:26 Oded Gabbay
2015-02-03 11:36 Oded Gabbay
2015-01-25 11:21 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=20150830094735.GA14904@odedg-home.redhat.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