From: Rusty Russell <rusty@rustcorp.com.au>
To: Jonathan Cameron <jic23@cam.ac.uk>, linux-kernel@vger.kernel.org
Cc: greg@kroah.com, adobriyan@gmail.com, Jonathan Cameron <jic23@cam.ac.uk>
Subject: Re: [RFC PATCH 0/3] Introduce kstrtobool function
Date: Thu, 24 Mar 2011 11:04:53 +1030 [thread overview]
Message-ID: <87oc51bbki.fsf@rustcorp.com.au> (raw)
In-Reply-To: <1300887554-19031-1-git-send-email-jic23@cam.ac.uk>
On Wed, 23 Mar 2011 13:39:11 +0000, Jonathan Cameron <jic23@cam.ac.uk> wrote:
> Dear all,
>
> This is an initial stab at a simple utility function intended to pin
> down what the kernel considers to be 'true' and 'false'. My original
> query was centered around processing of sysfs inputs but as Greg
> pointed out there are a couple of other places in kernel where this
> functionality would be useful.
Seems reasonable.
Rusty.
prev parent reply other threads:[~2011-03-24 2:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 13:39 [RFC PATCH 0/3] Introduce kstrtobool function Jonathan Cameron
2011-03-23 13:39 ` [PATCH 1/3] Add a kstrtobool function matching semantics of existing in kernel equivalents Jonathan Cameron
2011-03-23 13:54 ` David Sterba
2011-03-23 14:00 ` Jonathan Cameron
2011-03-23 15:30 ` Alexey Dobriyan
2011-03-23 16:01 ` Greg KH
2011-03-23 16:15 ` Jonathan Cameron
2011-03-23 16:23 ` Greg KH
2011-03-23 16:37 ` Jonathan Cameron
2011-03-23 18:44 ` Greg KH
2011-03-23 19:11 ` Jonathan Cameron
2011-03-23 13:39 ` [PATCH 2/3] debugfs: move to new kstrtobool function Jonathan Cameron
2011-03-23 20:20 ` Ryan Mallon
2011-03-24 10:53 ` Jonathan Cameron
2011-03-23 13:39 ` [PATCH 3/3] params.c: Use new kstrtobool implementation to processing boolean inputs Jonathan Cameron
2011-03-23 13:42 ` Jonathan Cameron
2011-03-24 0:34 ` Rusty Russell [this message]
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=87oc51bbki.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=adobriyan@gmail.com \
--cc=greg@kroah.com \
--cc=jic23@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.