From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Sumit Semwal <sumit.semwal@linaro.org>,
Thierry Reding <treding@nvidia.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the dma-buf tree
Date: Tue, 20 May 2014 10:26:44 +0200 [thread overview]
Message-ID: <537B11C4.2010406@canonical.com> (raw)
In-Reply-To: <20140520171351.736fb238@canb.auug.org.au>
Hey,
op 20-05-14 09:13, Stephen Rothwell schreef:
> Hi Sumit,
>
> After merging the dma-buf tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/gpu/drm/tegra/gem.c: In function 'tegra_gem_prime_export':
> drivers/gpu/drm/tegra/gem.c:423:15: error: macro "dma_buf_export" requires 5 arguments, but only 4 given
> drivers/gpu/drm/tegra/gem.c:422:9: error: 'dma_buf_export' undeclared (first use in this function)
>
> Caused by commit 8dfb1f0f8103 ("dma-buf: use reservation objects").
> Grep is your friend ...
>
> I have use the dma-buf tree from next-20140519 for today.
sumits can you amend the commit?
---
diff --git a/drivers/gpu/drm/tegra/gem.c b/drivers/gpu/drm/tegra/gem.c
index bcf9895cef9f..1e9de41a14ea 100644
--- a/drivers/gpu/drm/tegra/gem.c
+++ b/drivers/gpu/drm/tegra/gem.c
@@ -419,7 +419,7 @@ struct dma_buf *tegra_gem_prime_export(struct drm_device *drm,
int flags)
{
return dma_buf_export(gem, &tegra_gem_prime_dmabuf_ops, gem->size,
- flags);
+ flags, NULL);
}
struct drm_gem_object *tegra_gem_prime_import(struct drm_device *drm,
next prev parent reply other threads:[~2014-05-20 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 7:13 linux-next: build failure after merge of the dma-buf tree Stephen Rothwell
2014-05-20 8:26 ` Maarten Lankhorst [this message]
2014-05-20 9:09 ` Sumit Semwal
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=537B11C4.2010406@canonical.com \
--to=maarten.lankhorst@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sumit.semwal@linaro.org \
--cc=treding@nvidia.com \
/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.