[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190313161221.41797313@gandalf.local.home>
Date: Wed, 13 Mar 2019 16:12:21 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Rasmus Villemoes <linux@...musvillemoes.dk>
Cc: Nick Desaulniers <ndesaulniers@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
clang-built-linux@...glegroups.com,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
"# 3.4.x" <stable@...r.kernel.org>,
Nathan Chancellor <natechancellor@...il.com>,
Adhemerval Zanella <adhemerval.zanella@...aro.org>,
Arnd Bergmann <arnd@...db.de>,
James Y Knight <jyknight@...gle.com>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Ingo Molnar <mingo@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Dan Williams <dan.j.williams@...el.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] lib/string.c: implement a basic bcmp
On Wed, 13 Mar 2019 20:34:11 +0100
Rasmus Villemoes <linux@...musvillemoes.dk> wrote:
> Yes, but let's completely avoid mentioning memcmp in the summary.
>
> bcmp - return 0 if and only if the buffers have identical contents
> @a: pointer to first buffer
> @b: pointer to second buffer
> @len: size of buffers
>
> The sign or magnitude of a non-zero return value has no particular
> meaning, and architectures may implement their own more efficient
> bcmp(). So while this particular implementation is a simple (tail) call
> to memcmp, do not rely on anything but whether the return value is zero
> or non-zero.
Acked-by: Steven Rostedt (VMware) <rostedt@...dmis.org>
Thanks!
-- Steve
Powered by blists - more mailing lists