From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Andrew Morton <akpm@osdl.org>
Cc: holzheu@de.ibm.com, ioe-lkml@rameria.de,
linux-kernel@vger.kernel.org, mschwid2@de.ibm.com,
joern@wohnheim.fh-wedel.de
Subject: Re: [PATCH/RFC] s390: Hypervisor File System
Date: Tue, 25 Apr 2006 11:01:33 +0300 [thread overview]
Message-ID: <1145952094.11463.12.camel@localhost> (raw)
In-Reply-To: <20060425004736.451644bb.akpm@osdl.org>
Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> > +#ifndef __HAVE_ARCH_STRSTRIP
> > +extern char * strstrip(char *);
> > +#endif
On Tue, 2006-04-25 at 00:47 -0700, Andrew Morton wrote:
> Do we really need this gunk? It's not as if strstrip() is so super
> performance-sensitive that anyone would go and write a hand-tuned assembly
> version?
I guess not. I added it for consistency, but whatever makes you happy
Andrew :)
Pekka
diff --git a/include/linux/string.h b/include/linux/string.h
index c61306d..e4c7558 100644
--- a/include/linux/string.h
+++ b/include/linux/string.h
@@ -56,6 +56,7 @@ #endif
#ifndef __HAVE_ARCH_STRRCHR
extern char * strrchr(const char *,int);
#endif
+extern char * strstrip(char *);
#ifndef __HAVE_ARCH_STRSTR
extern char * strstr(const char *,const char *);
#endif
diff --git a/lib/string.c b/lib/string.c
index 064f631..6307726 100644
--- a/lib/string.c
+++ b/lib/string.c
@@ -301,6 +301,36 @@ char *strnchr(const char *s, size_t coun
EXPORT_SYMBOL(strnchr);
#endif
+/**
+ * strstrip - Removes leading and trailing whitespace from @s.
+ * @s: The string to be stripped.
+ *
+ * Note that the first trailing whitespace is replaced with a %NUL-terminator
+ * in the given string @s. Returns a pointer to the first non-whitespace
+ * character in @s.
+ */
+char *strstrip(char *s)
+{
+ size_t size;
+ char *end;
+
+ size = strlen(s);
+
+ if (!size)
+ return s;
+
+ end = s + size - 1;
+ while (end != s && isspace(*end))
+ end--;
+ *(end + 1) = '\0';
+
+ while (*s && isspace(*s))
+ s++;
+
+ return s;
+}
+EXPORT_SYMBOL(strstrip);
+
#ifndef __HAVE_ARCH_STRLEN
/**
* strlen - Find the length of a string
next prev parent reply other threads:[~2006-04-25 8:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 17:19 [PATCH/RFC] s390: Hypervisor File System Michael Holzheu
2006-04-25 6:58 ` Pekka Enberg
2006-04-25 7:32 ` Pekka Enberg
2006-04-25 7:47 ` Andrew Morton
2006-04-25 8:01 ` Pekka Enberg [this message]
2006-04-25 8:52 ` Jörn Engel
2006-04-25 9:00 ` Pekka Enberg
2006-04-25 12:22 ` Michael Holzheu
2006-04-25 14:33 ` Pekka Enberg
2006-04-25 14:45 ` Jörn Engel
2006-04-26 9:30 ` Michael Holzheu
-- strict thread matches above, loose matches on Subject: below --
2006-04-21 11:35 Michael Holzheu
2006-04-21 11:53 ` Pekka Enberg
2006-04-21 13:56 ` Michael Holzheu
2006-04-21 14:55 ` Arnd Bergmann
2006-04-21 15:31 ` Michael Holzheu
2006-04-21 13:32 ` Pekka Enberg
2006-04-21 14:08 ` Michael Holzheu
2006-04-21 15:38 ` Pekka Enberg
2006-04-21 16:40 ` Martin Schwidefsky
2006-04-25 14:04 ` Pekka Enberg
2006-04-21 14:42 ` Pekka Enberg
2006-04-21 14:59 ` Michael Holzheu
2006-04-21 15:41 ` Pekka Enberg
2006-04-21 15:18 ` Jörn Engel
2006-04-21 15:36 ` Michael Holzheu
2006-04-21 15:46 ` Jörn Engel
2006-04-21 22:30 ` Ingo Oeser
2006-04-24 17:17 ` Michael Holzheu
2006-04-24 19:57 ` Ingo Oeser
2006-04-25 6:27 ` Pekka Enberg
2006-04-24 17:19 ` Michael Holzheu
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=1145952094.11463.12.camel@localhost \
--to=penberg@cs.helsinki.fi \
--cc=akpm@osdl.org \
--cc=holzheu@de.ibm.com \
--cc=ioe-lkml@rameria.de \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mschwid2@de.ibm.com \
/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