[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160108131908.GB17997@ZenIV.linux.org.uk>
Date: Fri, 8 Jan 2016 13:19:08 +0000
From: Al Viro <viro@...IV.linux.org.uk>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Tejun Heo <tj@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
"David S . Miller" <davem@...emloft.net>,
David Airlie <airlied@...ux.ie>,
Andrew Morton <akpm@...ux-foundation.org>,
Rasmus Villemoes <linux@...musvillemoes.dk>
Subject: Re: [PATCH v3 0/9] lib/string: introduce match_string() helper
On Fri, Jan 08, 2016 at 03:09:09PM +0200, Andy Shevchenko wrote:
> There are users of a simple string matching in the array. Let's do a common
> helper for that.
What's the reason for making it return -ENODATA when no match is found?
That one of the callers wants to return that as error in such case?
At least one other is returning -EINVAL in the same situation...
Powered by blists - more mailing lists