From: Steven Rostedt <rostedt@goodmis.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Joe Perches <joe@perches.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Tom Zanussi <zanussi@kernel.org>,
Andreas Schwab <schwab@linux-m68k.org>,
kernel-team@lge.com
Subject: Re: [PATCH v4] string.h: Add str_has_prefix() helper function
Date: Sat, 22 Dec 2018 12:23:35 -0500 [thread overview]
Message-ID: <20181222122335.7fee7e5e@vmware.local.home> (raw)
In-Reply-To: <20181222121911.68603488@vmware.local.home>
On Sat, 22 Dec 2018 12:19:11 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> Because memcmp() isn't required to test byte by byte. In fact, most
> implementations don't which is why memcmp is faster than strcncmp.
In fact, if memcmp() was safe to use if we only knew the size of one of
the parameters, then there would be no reason for strncmp to exist.
-- Steve
next prev parent reply other threads:[~2018-12-22 17:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-22 4:19 [PATCH v4] string.h: Add str_has_prefix() helper function Steven Rostedt
2018-12-22 4:42 ` Steven Rostedt
2018-12-22 9:33 ` Namhyung Kim
2018-12-22 12:24 ` Steven Rostedt
2018-12-22 14:24 ` Namhyung Kim
2018-12-22 15:12 ` Steven Rostedt
2018-12-22 16:16 ` Steven Rostedt
2018-12-22 16:46 ` Namhyung Kim
2018-12-22 17:19 ` Steven Rostedt
2018-12-22 17:23 ` Steven Rostedt [this message]
2018-12-22 17:24 ` Steven Rostedt
2018-12-23 3:13 ` Namhyung Kim
2018-12-23 3:23 ` Steven Rostedt
2018-12-23 3:05 ` Namhyung Kim
2019-01-11 8:10 ` [utility perl script] strncmp() -> str_has_prefix() conversions Joe Perches
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=20181222122335.7fee7e5e@vmware.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=schwab@linux-m68k.org \
--cc=torvalds@linux-foundation.org \
--cc=zanussi@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