From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: stable@vger.kernel.org, "PÁLFFY Dániel" <dpalffy@gmail.com>,
Alsa-devel <alsa-devel@alsa-project.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"Mark Brown" <broonie@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Takashi Iwai" <tiwai@suse.com>,
"Richard Fitzgerald" <rf@opensource.cirrus.com>,
"Thorsten Leemhuis" <regressions@leemhuis.info>,
Sergey <zagagyka@basealt.ru>,
"Salvatore Bonaccorso" <carnil@debian.org>
Subject: Re: Request for cherry-picks for sound (Re: [regression, 5.10.y] Bug 216861)
Date: Wed, 4 Jan 2023 12:31:38 +0100 [thread overview]
Message-ID: <Y7Vjmod9m/Zmp4v2@kroah.com> (raw)
In-Reply-To: <87wn62obhm.wl-tiwai@suse.de>
On Wed, Jan 04, 2023 at 11:11:33AM +0100, Takashi Iwai wrote:
> Greg, just in case you missed my previous post.
>
> Could you cherry-pick the following two commits to 5.10.y and 5.15.y
> stable trees?
>
> e8444560b4d9302a511f0996f4cfdf85b628f4ca
> ASoC/SoundWire: dai: expand 'stream' concept beyond SoundWire
>
> 636110411ca726f19ef8e87b0be51bb9a4cdef06
> ASoC: Intel/SOF: use set_stream() instead of set_tdm_slots() for HDAudio
Took a bit of work, but both now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-01-04 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 8:08 [regression, 5.10.y] Bug 216861 - sound disappearance on Acer Swift 3 SF314-59-78UR after update to 5.10.157 Thorsten Leemhuis
2023-01-02 10:43 ` Salvatore Bonaccorso
2023-01-02 12:42 ` Takashi Iwai
[not found] ` <CALp6mkJhM1zDcNr9X_7WL09+uqcaAhNFFMhrjme0r7584O+Lgw@mail.gmail.com>
2023-01-03 13:04 ` PÁLFFY Dániel
2023-01-03 14:48 ` Takashi Iwai
2023-01-03 16:26 ` Takashi Iwai
2023-01-04 10:11 ` Request for cherry-picks for sound (Re: [regression, 5.10.y] Bug 216861) Takashi Iwai
2023-01-04 10:35 ` Linux kernel regression tracking (#info)
2023-01-04 11:31 ` 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=Y7Vjmod9m/Zmp4v2@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=carnil@debian.org \
--cc=dpalffy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=rf@opensource.cirrus.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=zagagyka@basealt.ru \
/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