From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: linux-kernel@vger.kernel.org
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Kees Cook <keescook@chromium.org>
Subject: memchr() vs. memscan()
Date: Thu, 2 Feb 2023 17:34:15 +0200 [thread overview]
Message-ID: <Y9vX95GpI272VKn0@smile.fi.intel.com> (raw)
Why do we have memchr() and memscan() implementations in lib/string.c?
As far as I can see the one may be derived from the other easily.
--
With Best Regards,
Andy Shevchenko
next reply other threads:[~2023-02-02 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 15:34 Andy Shevchenko [this message]
2023-02-03 7:18 ` Rasmus Villemoes
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=Y9vX95GpI272VKn0@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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®