From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jessica Yu <jeyu@redhat.com>, Andrew Morton <akpm@linux-foundation.org>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] Implement character sets for sscanf()
Date: Mon, 22 Feb 2016 11:27:14 +0200 [thread overview]
Message-ID: <1456133234.13244.16.camel@linux.intel.com> (raw)
In-Reply-To: <1455931259-27117-1-git-send-email-jeyu@redhat.com>
On Fri, 2016-02-19 at 20:20 -0500, Jessica Yu wrote:
> Hi,
>
> This patch adds support for the '%[' conversion specifier for
> sscanf().
> Since functions that calculate substring lengths based on accepted or
> rejected characters already exist in the kernel (namely strspn() and
> strcspn()), it's not much of a stretch to add some basic support for
> the
> bracket '%[' conversion specifier for sscanf(). This is useful in
> cases
> where we'd like to match substrings delimited by something other than
> spaces. The original motivation for this patch actually came from
> livepatch
> (https://lkml.org/lkml/2016/2/8/790), where we were trying to come up
> with
> a clean way to parse symbol names with substrings delimited by
> periods and
> commas.
>
> Patch based on linux-next-20160219.
>
> Here are some test cases:
Test cases should land into lib/test_scanf.c and be submitted as a
separate patch.
Also, you have something misconfigured when you sent patches. git-send-
email usually does a perfect job.
> ---
> sscanf_tests.c
> ---
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2016-02-22 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 1:20 [PATCH 0/1] Implement character sets for sscanf() Jessica Yu
2016-02-22 9:27 ` Andy Shevchenko [this message]
2016-02-22 19:39 ` Jessica Yu
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=1456133234.13244.16.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=jeyu@redhat.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;
as well as URLs for NNTP newsgroup(s).