From: Andries.Brouwer@cwi.nl
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] hpfs sparse fixes
Date: Mon, 29 Sep 2003 01:31:12 +0200 (MEST) [thread overview]
Message-ID: <UTC200309282331.h8SNVC705517.aeb@smtp.cwi.nl> (raw)
diff -u --recursive --new-file -X /linux/dontdiff a/fs/hpfs/file.c b/fs/hpfs/file.c
--- a/fs/hpfs/file.c Mon Sep 29 01:05:41 2003
+++ b/fs/hpfs/file.c Mon Sep 29 01:13:23 2003
@@ -124,7 +124,8 @@
.bmap = _hpfs_bmap
};
-ssize_t hpfs_file_write(struct file *file, const char *buf, size_t count, loff_t *ppos)
+ssize_t hpfs_file_write(struct file *file, const char __user *buf,
+ size_t count, loff_t *ppos)
{
ssize_t retval;
diff -u --recursive --new-file -X /linux/dontdiff a/fs/hpfs/hpfs_fn.h b/fs/hpfs/hpfs_fn.h
--- a/fs/hpfs/hpfs_fn.h Mon Sep 29 01:05:41 2003
+++ b/fs/hpfs/hpfs_fn.h Mon Sep 29 01:13:23 2003
@@ -249,7 +249,7 @@
secno hpfs_bmap(struct inode *, unsigned);
void hpfs_truncate(struct inode *);
int hpfs_get_block(struct inode *inode, sector_t iblock, struct buffer_head *bh_result, int create);
-ssize_t hpfs_file_write(struct file *file, const char *buf, size_t count, loff_t *ppos);
+ssize_t hpfs_file_write(struct file *file, const char __user *buf, size_t count, loff_t *ppos);
/* inode.c */
reply other threads:[~2003-09-28 23:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=UTC200309282331.h8SNVC705517.aeb@smtp.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®