From: Mark yao <mark.yao@rock-chips.com>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: list@263.net, open list <linux-kernel@vger.kernel.org>,
DRM DRIVERS <dri-devel@lists.freedesktop.org>,
linux-rockchip@lists.infradead.org, open@263.net,
Pawel Osciak <posciak@chromium.org>
Subject: [GIT PULL] drm/rockchip: fix dma_alloc_attrs() error check
Date: Fri, 09 Jan 2015 11:51:42 +0800 [thread overview]
Message-ID: <54AF504E.7030301@rock-chips.com> (raw)
In-Reply-To: <1420622830-8608-1-git-send-email-djkurtz@chromium.org>
Hi Dave
fix that: dma_alloc_attrs() returns NULL if it cannot allocate a
dma buffer (or mapping), not a negative error code.
The following changes since commit c93546a5e32bd788c22aefa072385f3784551c13:
Merge tag 'topic/atomic-core-2015-01-05' of
git://anongit.freedesktop.org/drm-intel into drm-next (2015-01-09
09:22:40 +1000)
are available in the git repository at:
https://github.com/markyzq/kernel-drm-rockchip.git drm-next
for you to fetch changes up to 4b9a90c0b374f8f7b3ceabe3c202424c98a6c5a4:
drm/rockchip: fix dma_alloc_attrs() error check (2015-01-09 11:29:06
+0800)
----------------------------------------------------------------
Daniel Kurtz (1):
drm/rockchip: fix dma_alloc_attrs() error check
drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 9 +++------
1 file changed, 3 insertions(+), 6 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-01-09 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 9:27 [PATCH] drm/rockchip: fix dma_alloc_attrs() error check Daniel Kurtz
2015-01-09 3:51 ` Mark yao [this message]
2015-01-09 4:01 ` Daniel Kurtz
2015-01-21 2:43 ` Daniel Kurtz
2015-01-21 2:48 ` 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=54AF504E.7030301@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=djkurtz@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=list@263.net \
--cc=open@263.net \
--cc=posciak@chromium.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