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: <20171115164109.gl6rxeofu3vjngt6@sasha-lappy>
Date:   Wed, 15 Nov 2017 16:41:13 +0000
From:   alexander.levin@...izon.com
To:     Jose Abreu <Jose.Abreu@...opsys.com>
CC:     Mark Brown <broonie@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: Re: [PATCH AUTOSEL for 4.9 44/56] ASoC: dwc: Fix PIO mode
 initialization

On Wed, Nov 15, 2017 at 02:06:45PM +0000, Jose Abreu wrote:
>
>
>On 15-11-2017 13:20, Mark Brown wrote:
>>
>> Why on earth would anyone use audio hardware without DMA in production
>> (or make it for that matter)?  Not that it really matters.
>
>That was my thought while I was implementing this. I guess HW
>guys had their reasons.
>
>>  Even if
>> there are users on stable presumably the they're already running with
>> something like this and it'll just conflict with this if it gets
>> backported?
>
>Probably yes. I was never contacted about this PIO driver so
>either they fixed it manually and never sent a patch or they are
>not using it.
>
>> The whole backport to enable a thing that never worked
>> aspect of this seems out of scope for stable.
>
>Ah, I reminded now that ARC PGU DRM driver (which is needed for
>I2S audio to work) is totally broken in 4.9 because of some DRM
>core changes and was never backported because the fix was simply
>too large.
>
>Yeah, I think given all these reasons we can drop this patch.

Will do. Thanks!

Just to clarify this for me, would you consider the patch, on it's
own, as stable material (ignoring this particular instance where
there was simply no reason to backport it)?

-- 

Thanks,
Sasha

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ