public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: x29a <0.x29a.0@googlemail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] w1: add ability to set (SRAM) and store (EEPROM) configuration for temp sensors like DS18B20
Date: Sun, 1 May 2016 14:03:47 -0700	[thread overview]
Message-ID: <20160501210347.GA32231@kroah.com> (raw)
In-Reply-To: <504421461755611@web6g.yandex.ru>

On Wed, Apr 27, 2016 at 02:13:31PM +0300, Evgeniy Polyakov wrote:
> Hi
> 
> 17.04.2016, 02:08, "x29a" <0.x29a.0@googlemail.com>:
> > based on the PR (https://github.com/raspberrypi/linux/pull/1412) for the raspberry pi kernel, i would like to propose my changes upstream as well.
> >
> > The changes entitle basic write operations for the 1Wire driver which are needed to change e.g. the precision of temperature sensors like the very popular DS18B20. Writing to SRAM and commiting the values to EEPROM is possible.
> >
> > Since many sensors come "preconfigured" with a lower precision, people are stuck that precision when running on a kernel based device (unlike the Dallas 1Wire library for e.g. Arduino, which supports writing the configuration/scratchpad).
> 
> This looks good to me, Greg, please pull it into your tree
> 
> > Signed-off-by: x29a <0.x29a.0@gmail.com>
> 
> Acked-by: Evgeniy Polyakov <zbr@ioremap.net>

I can't, I need a "real" name for a patch.

"x29a", can you resend this with your real name on it, and I will be
glad to apply it to the tree.

thanks,

greg k-h

      reply	other threads:[~2016-05-01 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-16 23:08 [PATCH] w1: add ability to set (SRAM) and store (EEPROM) configuration for temp sensors like DS18B20 x29a
2016-04-27 11:13 ` Evgeniy Polyakov
2016-05-01 21:03   ` Greg KH [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=20160501210347.GA32231@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=0.x29a.0@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zbr@ioremap.net \
    /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