From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: jack - check status of GPIO-based pins on resume
Date: Fri, 24 Mar 2017 12:22:09 -0700 [thread overview]
Message-ID: <20170324192209.GB18364@dtor-ws> (raw)
In-Reply-To: <20170324185147.rwbi2qqynr2yggq2@sirena.org.uk>
On Fri, Mar 24, 2017 at 06:51:47PM +0000, Mark Brown wrote:
> On Tue, Mar 21, 2017 at 04:50:43PM -0700, Dmitry Torokhov wrote:
> > From: Dmitry Torokhov <dtor@chromium.org>
> >
> > For GPIO-backed pins that are not configured as wakeup sources, we may
> > miss change in their state that happens while system is suspended. Let's
> > use PM notifier to refresh their state upon resume.
> >
> > Signed-off-by: Dmitry Torokhov <dtor@chromium.org>
> > ---
>
> Please send patches from the mail account corresponding to the signoff,
> not doing that makes the patch look like it's missing a signoff (as it's
> got the From line so more than one signoff is expected but there's only
> one) which slows down review.
Resent from @chromium.
--
Dmitry
next prev parent reply other threads:[~2017-03-24 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 23:50 [PATCH] ASoC: jack - check status of GPIO-based pins on resume Dmitry Torokhov
2017-03-24 18:51 ` Mark Brown
2017-03-24 19:22 ` Dmitry Torokhov [this message]
2017-03-24 19:26 ` Mark Brown
2017-03-24 19:28 ` Dmitry Torokhov
2017-03-24 19:16 ` Applied "ASoC: jack - check status of GPIO-based pins on resume" to the asoc tree Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2017-03-24 19:20 [PATCH] ASoC: jack - check status of GPIO-based pins on resume Dmitry Torokhov
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=20170324192209.GB18364@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.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).