From: Jean Delvare <khali@linux-fr.org>
To: Steve Hardy <steve@linuxrealtime.co.uk>
Cc: linux-kernel@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: [PATCH 1/1] : hwmon - new chip driver for TI ADS7828 A-D
Date: Tue, 15 Jan 2008 11:31:43 +0100 [thread overview]
Message-ID: <20080115113143.6a181fab@hyperion.delvare> (raw)
In-Reply-To: <20080114222849.GA7279@toshiba-lt>
Hi Steve,
On Mon, 14 Jan 2008 22:28:51 +0000, Steve Hardy wrote:
> > As far as I know boolean parameters take values 0 and 1, not N and Y.
>
> Not on the systems I am testing on (2.6.24-rc6) - the sysfs interface
> displays boolean parameters as Y/N, and will accept boot parameters as
> either Y/N or 0/1. Below is a snippet from a test proving this point :
>
> test@shtest:~$ cat /sys/module/ads7828/parameters/se_input
> Y
> test@shtest:~$ cat /sys/module/ads7828/parameters/int_vref
> Y
>
> after appending the ads7828.int_vref=N parameter to the kernel
> command-line :
>
> Linux 2.6.24-rc6 (shtest) (16:53 on Saturday, 05 January 2002)
>
> login: test
> test@shtest:~$ cat /sys/module/ads7828/parameters/int_vref
> N
Oh. This is news to me, thanks for the information.
> Is it more "correct" to refer to 1/0 in the documentation?
> I just naturally used the same syntax provided by the sysfs nodes
Nah, just scratch this comment of mine, I just didn't know that Y/N was
working for booleans. If you prefer that to document that form that's
alright with me.
(I do believe that it was a mistake to allow two different ways to do
the same thing, but that's a different issue.)
--
Jean Delvare
next prev parent reply other threads:[~2008-01-15 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <477D50CC.6020504@linuxrealtime.co.uk>
2008-01-04 7:34 ` [PATCH 1/1] : hwmon - new chip driver for TI ADS7828 A-D Steve Hardy
2008-01-10 0:30 ` Andrew Morton
2008-01-10 13:19 ` Jean Delvare
2008-01-14 22:28 ` Steve Hardy
2008-01-15 10:31 ` Jean Delvare [this message]
2007-12-03 17:59 Steve Hardy
2007-12-12 10:25 ` Andrew Morton
2007-12-18 20:56 ` Steve Hardy
2007-12-19 14:54 ` Jean Delvare
2007-12-19 15:35 ` Jean Delvare
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=20080115113143.6a181fab@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=steve@linuxrealtime.co.uk \
/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