From: Mike Frysinger <vapier@gentoo.org>
To: linux-kernel@vger.kernel.org
Subject: [PATCH v4] linux/uio.h: cleanup for userspace
Date: Mon, 29 Dec 2008 15:32:13 -0500 [thread overview]
Message-ID: <1230582733-8010-1-git-send-email-vapier@gentoo.org> (raw)
In-Reply-To: <20081229130353.GA10167@infradead.org>
Hide iov_shorten() behind __KERNEL__ since it's a prototype only. Use the
__inline__ form for iov_length() since it's usable by userspace.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
---
v4
- hide all funcs behind __KERNEL__
v3
- keep all __KERNEL__ stuff in one place
v2
- drop inline conversion stuff
include/linux/uio.h | 18 +++++++++---------
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/include/linux/uio.h b/include/linux/uio.h
index b7fe138..31d75cd 100644
--- a/include/linux/uio.h
+++ b/include/linux/uio.h
@@ -19,6 +19,13 @@ struct iovec
__kernel_size_t iov_len; /* Must be size_t (1003.1g) */
};
+/*
+ * UIO_MAXIOV shall be at least 16 1003.1g (5.4.1.1)
+ */
+
+#define UIO_FASTIOV 8
+#define UIO_MAXIOV 1024
+
#ifdef __KERNEL__
struct kvec {
@@ -26,15 +33,6 @@ struct kvec {
size_t iov_len;
};
-#endif
-
-/*
- * UIO_MAXIOV shall be at least 16 1003.1g (5.4.1.1)
- */
-
-#define UIO_FASTIOV 8
-#define UIO_MAXIOV 1024
-
/*
* Total number of bytes covered by an iovec.
*
@@ -55,3 +53,5 @@ static inline size_t iov_length(const struct iovec *iov, unsigned long nr_segs)
unsigned long iov_shorten(struct iovec *iov, unsigned long nr_segs, size_t to);
#endif
+
+#endif
--
1.6.0.6
prev parent reply other threads:[~2008-12-29 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-27 6:49 [PATCH] " Mike Frysinger
2008-12-29 12:20 ` [PATCH v2] " Mike Frysinger
2008-12-29 12:56 ` Sam Ravnborg
2008-12-29 12:59 ` [PATCH v3] " Mike Frysinger
2008-12-29 13:03 ` Christoph Hellwig
2008-12-29 20:32 ` Mike Frysinger [this message]
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=1230582733-8010-1-git-send-email-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®