public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: Dmitry Khromov <dk@icelogic.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] w1: introduce an ability to specify microseconds bus scanning intervals
Date: Wed, 13 May 2015 08:31:52 -0700	[thread overview]
Message-ID: <20150513153152.GA11677@kroah.com> (raw)
In-Reply-To: <5974311431529255@web10h.yandex.ru>

On Wed, May 13, 2015 at 06:00:55PM +0300, Evgeniy Polyakov wrote:
> Hi
> 
> 12.05.2015, 22:30, "Dmitry Khromov" <dk@icelogic.net>:
> > Some of 1-Wire devices commonly associated with physical access control
> > systems are attached/generate presence for as short as 100 ms - hence
> > the tens-to-hundreds milliseconds scan intervals are required.
> >
> > Signed-off-by: Dmitry Khromov <dk@icelogic.net>
> 
> Greg, please pull it upstream
> Acked-by: Evgeniy Polyakov <zbr@ioremap.net>

Ok, will do.

      reply	other threads:[~2015-05-13 15:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <55292A69.5020106@icelogic.net>
     [not found] ` <1040571428797306@web8j.yandex.ru>
2015-04-14  7:40   ` [PATCH] Introduce an ability to specify microseconds bus scanning intervals in w1 core Dmitry Khromov
2015-04-14 17:15     ` Randy Dunlap
2015-04-22 21:55       ` [PATCH v2] w1: introduce an ability to specify microseconds bus scanning intervals Dmitry Khromov
2015-04-22 23:22         ` Evgeniy Polyakov
2015-04-23  9:20         ` Greg KH
2015-04-23 11:30           ` Dmitry Khromov
2015-04-23 11:33             ` [PATCH v3] " Dmitry Khromov
2015-05-12 19:29           ` Dmitry Khromov
2015-05-13 15:00             ` Evgeniy Polyakov
2015-05-13 15:31               ` gregkh [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=20150513153152.GA11677@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dk@icelogic.net \
    --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