From: Jessica Yu <jeyu@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: sscanf: implement basic character sets
Date: Mon, 7 Mar 2016 18:12:20 -0500 [thread overview]
Message-ID: <20160307231220.GC12689@packer-debian-8-amd64.digitalocean.com> (raw)
In-Reply-To: <20160226202810.GA6566@packer-debian-8-amd64.digitalocean.com>
+++ Jessica Yu [26/02/16 15:28 -0500]:
>+++ Jessica Yu [26/02/16 15:20 -0500]:
>>Implement basic character sets for the '%[' conversion specifier.
>>
>>The '%[' conversion specifier matches a nonempty sequence of characters
>>from the specified set of accepted (or with '^', rejected) characters
>>between the brackets. The substring matched is to be made up of characters
>>in (or not in) the set. This is useful for matching substrings that are
>>delimited by something other than spaces.
>>
>>This implementation differs from its glibc counterpart in the following ways:
>>(1) No support for character ranges (e.g., 'a-z' or '0-9')
>>(2) The hyphen '-' is not a special character
>>(3) The closing bracket ']' cannot be matched
>>(4) No support (yet) for discarding matching input ('%*[')
>>
>>Signed-off-by: Jessica Yu <jeyu@redhat.com>
>
>Since this version is largely based on Rasmus' sample bitmap code
>(with only very minor tweaks), what is the best way to provide
>attribution in this case? A Suggested-by: tag or another
>Signed-off-by: tag (since actual code is involved)?
Andrew, friendly ping on this patch and question? :-)
Thanks,
Jessica
next prev parent reply other threads:[~2016-03-07 23:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 20:20 [PATCH v4] " Jessica Yu
2016-02-26 20:28 ` Jessica Yu
2016-03-07 23:12 ` Jessica Yu [this message]
2016-03-07 23:24 ` Andrew Morton
2016-03-07 23:32 ` Rasmus Villemoes
2016-03-08 1:07 ` Jessica Yu
2016-03-02 23:49 ` [PATCH v4] " Rasmus Villemoes
2016-03-07 23:09 ` Jessica Yu
-- strict thread matches above, loose matches on Subject: below --
2016-04-05 14:32 [PATCH v4] " Shahbaz Youssefi
2016-04-05 17:25 ` Jessica Yu
2016-02-23 20:38 [PATCH v3] " Jessica Yu
2016-02-23 22:05 ` Andrew Morton
2016-02-24 5:13 ` Jessica Yu
2016-02-24 5:28 ` Andrew Morton
2016-02-23 22:47 ` [PATCH v3] " Rasmus Villemoes
2016-02-24 5:39 ` Jessica Yu
2016-02-22 21:24 [PATCH v2] " Jessica Yu
2016-02-23 10:56 ` Andy Shevchenko
2016-02-23 19:00 ` Kees Cook
2016-02-23 19:40 ` Jessica Yu
2016-02-23 19:26 ` Jessica Yu
2016-02-20 1:22 [PATCH 1/1] " Jessica Yu
2016-02-22 10:13 ` Andy Shevchenko
2016-02-22 17:51 ` 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=20160307231220.GC12689@packer-debian-8-amd64.digitalocean.com \
--to=jeyu@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.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®