From: YAMANE Toshiaki <yamanetoshi@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Rob Clark <rob@ti.com>
Cc: Dave Airlie <airlied@redhat.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
YAMANE Toshiaki <yamanetoshi@gmail.com>
Subject: [PATCH 12/16] staging/omapdrm: Fix spacing coding style in omap_gem_dmabuf.c
Date: Wed, 14 Nov 2012 19:40:14 +0900 [thread overview]
Message-ID: <1352889614-16052-1-git-send-email-yamanetoshi@gmail.com> (raw)
In-Reply-To: <1352888935-14742-1-git-send-email-yamanetoshi@gmail.com>
The following errors fixed.
- ERROR: "foo * bar" should be "foo *bar"
Signed-off-by: YAMANE Toshiaki <yamanetoshi@gmail.com>
---
drivers/staging/omapdrm/omap_gem_dmabuf.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/omapdrm/omap_gem_dmabuf.c b/drivers/staging/omapdrm/omap_gem_dmabuf.c
index c6f3ef6..9a30206 100644
--- a/drivers/staging/omapdrm/omap_gem_dmabuf.c
+++ b/drivers/staging/omapdrm/omap_gem_dmabuf.c
@@ -191,13 +191,13 @@ struct dma_buf_ops omap_dmabuf_ops = {
.mmap = omap_gem_dmabuf_mmap,
};
-struct dma_buf * omap_gem_prime_export(struct drm_device *dev,
+struct dma_buf *omap_gem_prime_export(struct drm_device *dev,
struct drm_gem_object *obj, int flags)
{
return dma_buf_export(obj, &omap_dmabuf_ops, obj->size, 0600);
}
-struct drm_gem_object * omap_gem_prime_import(struct drm_device *dev,
+struct drm_gem_object *omap_gem_prime_import(struct drm_device *dev,
struct dma_buf *buffer)
{
struct drm_gem_object *obj;
--
1.7.9.5
next prev parent reply other threads:[~2012-11-14 10:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 10:28 [PATCH 01/16] staging/omapdrm: Fix spacing coding style in omap_connector.c YAMANE Toshiaki
2012-11-14 10:30 ` [PATCH 02/16] staging/omapdrm: remove the unnecessary initialization of a local variable in omap_crtc.c YAMANE Toshiaki
2012-11-14 10:30 ` [PATCH 03/16] staging/omapdrm: Fix spacing coding style " YAMANE Toshiaki
2012-11-14 10:30 ` [PATCH 04/16] staging/omapdrm: Fix spacing coding style in omap_drv.c YAMANE Toshiaki
2012-11-14 10:30 ` [PATCH 05/16] staging/omapdrm: Fix spacing coding style in omap_drv.h YAMANE Toshiaki
2012-11-14 10:31 ` [PATCH 06/16] " YAMANE Toshiaki
2012-11-14 10:31 ` [PATCH 07/16] staging/omapdrm: Fix spacing coding style in omap_encoder.c YAMANE Toshiaki
2012-11-14 10:32 ` [PATCH 08/16] staging/omapdrm: Fix spacing coding style in omap_fb.c YAMANE Toshiaki
2012-11-14 10:32 ` [PATCH 09/16] staging/omapdrm: Fix spacing coding style in omap_gem.c YAMANE Toshiaki
2012-11-14 10:33 ` [PATCH 10/16] " YAMANE Toshiaki
2012-11-14 10:33 ` [PATCH 11/16] " YAMANE Toshiaki
2012-11-14 10:40 ` YAMANE Toshiaki [this message]
2012-11-14 10:40 ` [PATCH 13/16] staging/omapdrm: Fix spacing coding style in omap_gem_helper.c YAMANE Toshiaki
2012-11-14 10:40 ` [PATCH 14/16] " YAMANE Toshiaki
2012-11-14 10:40 ` [PATCH 15/16] staging/omapdrm: Fix spacing coding style in omap_plane.c YAMANE Toshiaki
2012-11-14 10:41 ` [PATCH 16/16] " YAMANE Toshiaki
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=1352889614-16052-1-git-send-email-yamanetoshi@gmail.com \
--to=yamanetoshi@gmail.com \
--cc=airlied@redhat.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@ti.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 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).