[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1401310243090.7183@chino.kir.corp.google.com>
Date: Fri, 31 Jan 2014 02:46:08 -0800 (PST)
From: David Rientjes <rientjes@...gle.com>
To: Pavel Machek <pavel@....cz>
cc: Sebastian Capella <sebastian.capella@...aro.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-pm@...r.kernel.org, linaro-kernel@...ts.linaro.org,
patches@...aro.org, Andrew Morton <akpm@...ux-foundation.org>,
Michel Lespinasse <walken@...gle.com>,
Shaohua Li <shli@...nel.org>,
Jerome Marchand <jmarchan@...hat.com>,
Mikulas Patocka <mpatocka@...hat.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>
Subject: Re: [PATCH v4 1/2] mm: add kstrimdup function
On Fri, 31 Jan 2014, Pavel Machek wrote:
> > kstrimdup will duplicate and trim spaces from the passed in
> > null terminated string. This is useful for strings coming from
> > sysfs that often include trailing whitespace due to user input.
>
> Is it good idea? I mean "\n\n/foo bar baz" is valid filename in
> unix. This is kernel interface, it is not meant to be too user
> friendly...
v6 of this patchset carries your ack of the patch that uses this for
/sys/debug/resume, so are you disagreeing we need this support at all or
that it shouldn't be the generic sysfs write behavior? If the latter, I
agree, and the changelog could be improved to specify what writes we
actually care about.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists