From: Sanjeev Premi <premi@ti.com>
To: linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org
Cc: Sanjeev Premi <premi@ti.com>
Subject: [PATCH] omap2/3: mtd: fix compile warning
Date: Tue, 29 Dec 2009 16:04:52 +0530 [thread overview]
Message-ID: <1262082892-5260-1-git-send-email-premi@ti.com> (raw)
This patch fixes following compile warning:
drivers/mtd/nand/omap2.c:508: warning: passing argumen
t 2 of 'omap_nand_dma_transfer' discards qualifiers fr
om pointer target type
Signed-off-by: Sanjeev Premi <premi@ti.com>
---
drivers/mtd/nand/omap2.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
index 1bb799f..08c193c 100644
--- a/drivers/mtd/nand/omap2.c
+++ b/drivers/mtd/nand/omap2.c
@@ -505,7 +505,7 @@ static void omap_write_buf_dma_pref(struct mtd_info *mtd,
omap_write_buf_pref(mtd, buf, len);
else
/* start transfer in DMA mode */
- omap_nand_dma_transfer(mtd, buf, len, 0x1);
+ omap_nand_dma_transfer(mtd, (void *)buf, len, 0x1);
}
/**
--
1.6.2.2
next reply other threads:[~2009-12-29 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 10:34 Sanjeev Premi [this message]
2010-01-10 8:48 ` [PATCH] omap2/3: mtd: fix compile warning Artem Bityutskiy
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=1262082892-5260-1-git-send-email-premi@ti.com \
--to=premi@ti.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.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