From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: John Keeping <john@metanate.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Michael Tretter <m.tretter@pengutronix.de>,
Andrej Valek <andrej.valek@siemens.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: st1232 - prefer asynchronous probing
Date: Mon, 11 Oct 2021 18:31:53 -0700 [thread overview]
Message-ID: <YWTlidGfIGXukwCC@google.com> (raw)
In-Reply-To: <20211007111217.1935858-1-john@metanate.com>
On Thu, Oct 07, 2021 at 12:12:16PM +0100, John Keeping wrote:
> The device may take up to 100ms to become responsive during probe, so
> prefer asynchronous probing to avoid delaying the rest of the system.
>
> Suggested-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Signed-off-by: John Keeping <john@metanate.com>
Applied, thank you.
--
Dmitry
prev parent reply other threads:[~2021-10-12 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 11:12 [PATCH] Input: st1232 - prefer asynchronous probing John Keeping
2021-10-12 1:31 ` Dmitry Torokhov [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=YWTlidGfIGXukwCC@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=andrej.valek@siemens.com \
--cc=geert+renesas@glider.be \
--cc=john@metanate.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).