All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <patchwork-2CcfMPLixEJMOuyiOMDZUm2NpIq0e7HX@public.gmane.org>
To: David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Koichi Yasutake
	<yasutake.koichi-NAum8xwdG0+S7A1Ibl2khg@public.gmane.org>,
	linux-am33-list-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>,
	Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Subject: [PATCH] mn10300: Wire up mn10300_dma_supported
Date: Mon, 25 Jan 2016 22:55:43 -0800	[thread overview]
Message-ID: <1453791343-12383-1-git-send-email-patchwork@patchwork.roeck-us.net> (raw)

From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>

Commit f151341ca00e ("mn10300: convert to dma_map_ops") declares
mn10300_dma_supported, but does not wire it up. This results in
the following build warning.

arch/mn10300/mm/dma-alloc.c: warning:
	'mn10300_dma_supported' defined but not used

Fixes: f151341ca00e ("mn10300: convert to dma_map_ops")
Cc: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Signed-off-by: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
---
 arch/mn10300/mm/dma-alloc.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/mn10300/mm/dma-alloc.c b/arch/mn10300/mm/dma-alloc.c
index 8842394cb49a..5ff49d67f55a 100644
--- a/arch/mn10300/mm/dma-alloc.c
+++ b/arch/mn10300/mm/dma-alloc.c
@@ -128,4 +128,5 @@ struct dma_map_ops mn10300_dma_ops = {
 	.map_sg			= mn10300_dma_map_sg,
 	.sync_single_for_device	= mn10300_dma_sync_single_for_device,
 	.sync_sg_for_device	= mn10300_dma_sync_sg_for_device,
+	.dma_supported		= mn10300_dma_supported,
 };
-- 
2.1.4

WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <patchwork@patchwork.roeck-us.net>
To: David Howells <dhowells@redhat.com>
Cc: Koichi Yasutake <yasutake.koichi@jp.panasonic.com>,
	linux-am33-list@redhat.com, linux-kernel@vger.kernel.org,
	kernel-testers@vger.kernel.org,
	Guenter Roeck <linux@roeck-us.net>,
	Christoph Hellwig <hch@lst.de>
Subject: [PATCH] mn10300: Wire up mn10300_dma_supported
Date: Mon, 25 Jan 2016 22:55:43 -0800	[thread overview]
Message-ID: <1453791343-12383-1-git-send-email-patchwork@patchwork.roeck-us.net> (raw)

From: Guenter Roeck <linux@roeck-us.net>

Commit f151341ca00e ("mn10300: convert to dma_map_ops") declares
mn10300_dma_supported, but does not wire it up. This results in
the following build warning.

arch/mn10300/mm/dma-alloc.c: warning:
	'mn10300_dma_supported' defined but not used

Fixes: f151341ca00e ("mn10300: convert to dma_map_ops")
Cc: Christoph Hellwig <hch@lst.de>
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
---
 arch/mn10300/mm/dma-alloc.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/mn10300/mm/dma-alloc.c b/arch/mn10300/mm/dma-alloc.c
index 8842394cb49a..5ff49d67f55a 100644
--- a/arch/mn10300/mm/dma-alloc.c
+++ b/arch/mn10300/mm/dma-alloc.c
@@ -128,4 +128,5 @@ struct dma_map_ops mn10300_dma_ops = {
 	.map_sg			= mn10300_dma_map_sg,
 	.sync_single_for_device	= mn10300_dma_sync_single_for_device,
 	.sync_sg_for_device	= mn10300_dma_sync_sg_for_device,
+	.dma_supported		= mn10300_dma_supported,
 };
-- 
2.1.4

             reply	other threads:[~2016-01-26  6:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26  6:55 Guenter Roeck [this message]
2016-01-26  6:55 ` [PATCH] mn10300: Wire up mn10300_dma_supported Guenter Roeck
2016-01-26 16:55 ` Christoph Hellwig

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=1453791343-12383-1-git-send-email-patchwork@patchwork.roeck-us.net \
    --to=patchwork-2ccfmplixejmouyiomdzum2npiq0e7hx@public.gmane.org \
    --cc=dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=hch-jcswGhMUV9g@public.gmane.org \
    --cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org \
    --cc=linux-am33-list-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=yasutake.koichi-NAum8xwdG0+S7A1Ibl2khg@public.gmane.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 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.