From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-input@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 1/2] Input: wm831x-ts - Ensure the controller is in a known state on open
Date: Tue, 15 Mar 2011 23:31:34 -0700 [thread overview]
Message-ID: <20110316063134.GF14604@core.coreip.homeip.net> (raw)
In-Reply-To: <1300142701-22260-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Mon, Mar 14, 2011 at 10:45:00PM +0000, Mark Brown wrote:
> Explicitly set all the enable bits when opening the device just in case
> something left the device in an unexpected state.
>
Applied, thank you Mark.
--
Dmitry
prev parent reply other threads:[~2011-03-16 6:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 22:45 [PATCH 1/2] Input: wm831x-ts - Ensure the controller is in a known state on open Mark Brown
2011-03-14 22:45 ` [PATCH 2/2] Input: wm831x-ts - Fix races with IRQ management Mark Brown
2011-03-18 11:20 ` Mark Brown
2011-03-25 7:30 ` Dmitry Torokhov
2011-03-25 10:49 ` Mark Brown
2011-03-16 6: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=20110316063134.GF14604@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-input@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
/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).