From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 6/9] sata_dwc: Make sata_write() use const void, per <part.h>
Date: Sat, 29 Sep 2012 13:51:53 -0700 [thread overview]
Message-ID: <1348951916-3495-7-git-send-email-trini@ti.com> (raw)
In-Reply-To: <1348951916-3495-1-git-send-email-trini@ti.com>
Signed-off-by: Tom Rini <trini@ti.com>
---
drivers/block/sata_dwc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/sata_dwc.c b/drivers/block/sata_dwc.c
index 75101b5..cc4446a 100644
--- a/drivers/block/sata_dwc.c
+++ b/drivers/block/sata_dwc.c
@@ -1907,7 +1907,7 @@ err_out:
#define SATA_MAX_WRITE_BLK 0xFFFF
#endif
-ulong sata_write(int device, ulong blknr, lbaint_t blkcnt, void *buffer)
+ulong sata_write(int device, ulong blknr, lbaint_t blkcnt, const void *buffer)
{
ulong start,blks, buf_addr;
unsigned short smallblks;
--
1.7.9.5
next prev parent reply other threads:[~2012-09-29 20:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-29 20:51 [U-Boot] [PATCH v1 0/9] block: Fix some inconsistencies in block_{read, write} implementors Tom Rini
2012-09-29 20:51 ` [U-Boot] [PATCH v1 1/9] ata_piix: Fix checkpatch issues Tom Rini
2012-09-29 20:51 ` [U-Boot] [PATCH v1 2/9] ata_piix: sata_write must take a const void argument Tom Rini
2012-09-29 20:51 ` [U-Boot] [PATCH v1 3/9] dwc_ahsata: Make sata_write() comply with <part.h> Tom Rini
2012-09-30 9:01 ` stefano babic
2012-09-29 20:51 ` [U-Boot] [PATCH v1 4/9] fsl_sata: Make sata_{read, write}() " Tom Rini
2012-09-29 20:51 ` [U-Boot] [PATCH v1 5/9] pata_bfin: " Tom Rini
2012-09-29 20:51 ` Tom Rini [this message]
2012-09-29 20:51 ` [U-Boot] [PATCH v1 7/9] sil_sata: Make sata_write() " Tom Rini
2012-09-29 20:51 ` [U-Boot] [PATCH v1 8/9] ide.h: Make ide_(read|write) match block_dev_desc_t block_(read|write) Tom Rini
2012-09-29 20:51 ` [U-Boot] [PATCH v1 9/9] sata.h: Make all sata/ata drivers include <sata.h> Tom Rini
2012-10-09 17:14 ` [U-Boot] [PATCH v1 0/9] block: Fix some inconsistencies in block_{read, write} implementors Tom Rini
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=1348951916-3495-7-git-send-email-trini@ti.com \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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