linux-kernel - Re: [PATCH 4.19 102/219] ALSA: hda/hdmi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20191230140304.GB1054989@kroah.com>
Date:   Mon, 30 Dec 2019 15:03:04 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Kai Vehmanen <kai.vehmanen@...ux.intel.com>
Cc:     Pavel Machek <pavel@...x.de>, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org, Takashi Iwai <tiwai@...e.de>,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        Mark Brown <broonie@...nel.org>,
        Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 4.19 102/219] ALSA: hda/hdmi - implement
 mst_no_extra_pcms flag

On Mon, Dec 30, 2019 at 03:01:52PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Dec 30, 2019 at 02:58:25PM +0200, Kai Vehmanen wrote:
> > Hi,
> > 
> > On Mon, 30 Dec 2019, Pavel Machek wrote:
> > 
> > > > From: Kai Vehmanen <kai.vehmanen@...ux.intel.com>
> > > > 
> > > > [ Upstream commit 2a2edfbbfee47947dd05f5860c66c0e80ee5e09d ]
> > > > 
> > > > To support the DP-MST multiple streams via single connector feature,
> > > > the HDMI driver was extended with the concept of backup PCMs. See
> > > > commit 9152085defb6 ("ALSA: hda - add DP MST audio support").
> > [...]
> > > This variable is not ever set in this patch, nor is it set elsewhere
> > > in 4.19-stable. This means this patch is not suitable for stable.
> > 
> > ack on that. In upstream this flag is only used by SOF (sound/soc/sof)
> > currently, but SOF is not part of 4.19, so there are no users for this 
> > flag. Sorry for not catching this sooner.
> 
> Will go drop it from 4.19.y, thanks.  But is this ok also for 5.4.y?

To answer my own question, no, it is not set there either, so I will
drop it from there as well.

thanks,

greg k-h