All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Gyeongtaek Lee <gt82.lee@samsung.com>
Cc: stable@vger.kernel.org, broonie@kernel.org, tiwai@suse.com,
	tkjung@samsung.com, hmseo@samsung.com, kimty@samsung.com
Subject: Re: [PATCH 0/4] Fixes for ASoC DPCM and topology
Date: Tue, 14 Apr 2020 10:15:10 +0200	[thread overview]
Message-ID: <20200414081510.GA4149624@kroah.com> (raw)
In-Reply-To: <000401d611fe$dd1589f0$97409dd0$@samsung.com>

On Tue, Apr 14, 2020 at 10:48:57AM +0900, Gyeongtaek Lee wrote:
> Hi,
> 
> I'd like to request cherry-picking some fixes for ALSA SoC to stable branch.
> Those patches are fix or add couple of functions which are essential when ALSA topology and Compress offload is used with Dynamic
> PCM.
> All fixes are tested on 4.19 and 5.4.
> 
> 1. Fix overflow of register mask when shift value is set to 32.
> 2. Default value setting for virtual kcontrol
> 3. Error on offload playback start or stop after pause
> 4. Prefix missing when a kcontrol is created with ASoC component with name prefix.
> 
> Commit ID:
>   0ab070917afdc93670c2d0ea02ab6defb6246a7c
>   3bbbb7728fc853d71dbce4073fef9f281fbfb4dd
>   21fca8bdbb64df1297e8c65a746c4c9f4a689751
>   abca9e4a04fbe9c6df4d48ca7517e1611812af25
> 
> Kernel version wish it to be applied:
>   5.4

Given these showed up in 5.7-rc1, they also need to go to 5.5.y and
5.6.y as those trees are currently active.  You can not have someone
upgrade from one stable release to another one and have a regression.

thanks,

greg k-h

  reply	other threads:[~2020-04-14  8:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200414014858epcas2p3e9028454a601cd9852ba6444f183d8c9@epcas2p3.samsung.com>
2020-04-14  1:48 ` [PATCH 0/4] Fixes for ASoC DPCM and topology Gyeongtaek Lee
2020-04-14  8:15   ` Greg KH [this message]
2020-04-14  8:16   ` Greg KH
2020-04-14  8:25     ` Greg KH
2020-04-14  8:50     ` Gyeongtaek Lee

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=20200414081510.GA4149624@kroah.com \
    --to=greg@kroah.com \
    --cc=broonie@kernel.org \
    --cc=gt82.lee@samsung.com \
    --cc=hmseo@samsung.com \
    --cc=kimty@samsung.com \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=tkjung@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.