[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170217095441.ceb0b055a2a967ff6c857b50@skyboo.net>
Date: Fri, 17 Feb 2017 09:54:41 +0100
From: Mariusz Bialonczyk <manio@...boo.net>
To: linux-kernel@...r.kernel.org, Evgeniy Polyakov <zbr@...emap.net>
Subject: Re: [PATCH 1/4] Documentation: w1_therm: clearly state about binary
value for precision
On Thu, 16 Feb 2017 10:05:36 +0100
Mariusz Bialonczyk <manio@...boo.net> wrote:
> Signed-off-by: Mariusz Bialonczyk <manio@...boo.net>
> ---
> Documentation/w1/slaves/w1_therm | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/w1/slaves/w1_therm b/Documentation/w1/slaves/w1_therm
> index d1f93af..e10cd91 100644
> --- a/Documentation/w1/slaves/w1_therm
> +++ b/Documentation/w1/slaves/w1_therm
> @@ -42,6 +42,7 @@ SRAM, so it is reset when the sensor gets power-cycled.
> To store the current precision configuration into EEPROM, the value 0
> has to be written to the sysfs w1_slave file. Since the EEPROM has a limited
> amount of writes (>50k), this command should be used wisely.
> +Note: this precision value has to be a binary one-byte value, not ASCII.
>
> The module parameter strong_pullup can be set to 0 to disable the
> strong pullup, 1 to enable autodetection or 2 to force strong pullup.
> --
> 2.9.3
>
Please skip this single patch. I was wrong about it.
w1_slave_store is using kstrtoint() so it is currently ok.
regards,
--
Mariusz Białończyk | xmpp/e-mail: manio@...boo.net
http://manio.skyboo.net | https://github.com/manio
Powered by blists - more mailing lists