From: re.emese@gmail.com
To: linux-kernel@vger.kernel.org
Cc: Emese Revfy <re.emese@gmail.com>,
sfr@canb.auug.org.au, benh@kernel.crashing.org, gregkh@suse.de,
geoffrey.levand@am.sony.com, torvalds@linux-foundation.org
Subject: [PATCH 05/10] Constify struct dma_map_ops for 2.6.32-git-053fe57ac v2
Date: Mon, 14 Dec 2009 00:59:20 +0100 [thread overview]
Message-ID: <c3fc8eaec7176bccaa9f3259a05af67385380088.1260662996.git.re.emese@gmail.com> (raw)
In-Reply-To: <cover.1260662995.git.re.emese@gmail.com>
From: Emese Revfy <re.emese@gmail.com>
Signed-off-by: Emese Revfy <re.emese@gmail.com>
---
arch/powerpc/platforms/ps3/system-bus.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/platforms/ps3/system-bus.c b/arch/powerpc/platforms/ps3/system-bus.c
index e34b305..20e48ec 100644
--- a/arch/powerpc/platforms/ps3/system-bus.c
+++ b/arch/powerpc/platforms/ps3/system-bus.c
@@ -694,7 +694,7 @@ static int ps3_dma_supported(struct device *_dev, u64 mask)
return mask >= DMA_BIT_MASK(32);
}
-static struct dma_map_ops ps3_sb_dma_ops = {
+static const struct dma_map_ops ps3_sb_dma_ops = {
.alloc_coherent = ps3_alloc_coherent,
.free_coherent = ps3_free_coherent,
.map_sg = ps3_sb_map_sg,
@@ -704,7 +704,7 @@ static struct dma_map_ops ps3_sb_dma_ops = {
.unmap_page = ps3_unmap_page,
};
-static struct dma_map_ops ps3_ioc0_dma_ops = {
+static const struct dma_map_ops ps3_ioc0_dma_ops = {
.alloc_coherent = ps3_alloc_coherent,
.free_coherent = ps3_free_coherent,
.map_sg = ps3_ioc0_map_sg,
--
1.6.5.3
next prev parent reply other threads:[~2009-12-14 0:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 23:59 [PATCH 00/10] " re.emese
2009-12-13 23:59 ` [PATCH 01/10] " re.emese
2009-12-13 23:59 ` [PATCH 02/10] " re.emese
2009-12-13 23:59 ` [PATCH 03/10] " re.emese
2009-12-13 23:59 ` [PATCH 04/10] " re.emese
2009-12-13 23:59 ` [PATCH 1/3] Constify struct block_device_operations " re.emese
2009-12-13 23:59 ` re.emese [this message]
2009-12-13 23:59 ` [PATCH 06/10] Constify struct dma_map_ops " re.emese
2009-12-13 23:59 ` [PATCH 2/3] Constify struct block_device_operations " re.emese
2009-12-13 23:59 ` [PATCH 3/3] " re.emese
2009-12-13 23:59 ` [PATCH 07/10] Constify struct dma_map_ops " re.emese
2009-12-13 23:59 ` [PATCH 08/10] " re.emese
2009-12-13 23:59 ` [PATCH 09/10] " re.emese
2009-12-13 23:59 ` [PATCH 10/10] " re.emese
2009-12-14 10:10 ` [PATCH 0/3] Constify struct block_device_operations " Joerg Roedel
2009-12-14 22:55 ` Emese Revfy
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=c3fc8eaec7176bccaa9f3259a05af67385380088.1260662996.git.re.emese@gmail.com \
--to=re.emese@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=geoffrey.levand@am.sony.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®