stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: stable@vger.kernel.org, Hui Wang <hui.wang@canonical.com>
Subject: Re: Cherry-pick two ALSA fixes for stable
Date: Tue, 26 Mar 2019 09:27:20 +0900	[thread overview]
Message-ID: <20190326002720.GA5112@kroah.com> (raw)
In-Reply-To: <s5hwokmmtut.wl-tiwai@suse.de>

On Tue, Mar 26, 2019 at 12:12:26AM +0100, Takashi Iwai wrote:
> On Mon, 25 Mar 2019 20:49:39 +0100,
> Greg Kroah-Hartman wrote:
> > 
> > On Mon, Mar 25, 2019 at 08:45:26AM +0100, Takashi Iwai wrote:
> > > Hi Greg,
> > > 
> > > could you cherry-pick two commits for ALSA fixes to stable tree(s)?
> > > 
> > > The first one is the commit
> > > 744c67ffeb06f2d2493f4049ba0bd19698ce0adf
> > >     ALSA: hda - Don't trigger jackpoll_work in azx_resume
> > > 
> > > and this is only for 5.0.x.
> > 
> > Now queued up.
> > 
> > > The second one is the commit
> > > b5a236c175b0d984552a5f7c9d35141024c2b261
> > >     ALSA: hda - Enforces runtime_resume after S3 and S4 for each codec
> > > 
> > > which is a fix up to 4.1, but this can be applied cleanly only to
> > > recent kernels, supposedly.
> > 
> > This one does not apply at all even to 5.0.y, sorry.  Can someone send a
> > backported version that I can apply?
> 
> There is a prerequisite commit
> 98081ca62cbac31fb0f7efaf90b2e7384ce22257
>     ALSA: hda - Record the current power state before suspend/resume calls
>     
> Could you apply this one as well, then?

Yes, that worked, thanks!

greg k-h

      reply	other threads:[~2019-03-26  0:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25  7:45 Cherry-pick two ALSA fixes for stable Takashi Iwai
2019-03-25 19:49 ` Greg Kroah-Hartman
2019-03-25 23:12   ` Takashi Iwai
2019-03-26  0:27     ` Greg Kroah-Hartman [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=20190326002720.GA5112@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=hui.wang@canonical.com \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.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).