linux-kernel - Re: Applied "ASoC: rockchip-max98090: Fix NULL pointer dereference while accessing to jack." to the asoc tree

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] [day] [month] [year] [list]

Message-ID: <CAFqH_52bVUgUgeHWTo8mcQh16c1W7uPMRqQ-RpgMdGusk=p=Og@mail.gmail.com>
Date:	Mon, 4 Jul 2016 17:13:05 +0200
From:	Enric Balletbo Serra <eballetbo@...il.com>
To:	Mark Brown <broonie@...nel.org>
Cc:	Enric Balletbo i Serra <enric.balletbo@...labora.com>,
	linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org,
	alsa-devel@...a-project.org, Heiko Stuebner <heiko@...ech.de>
Subject: Re: Applied "ASoC: rockchip-max98090: Fix NULL pointer dereference
 while accessing to jack." to the asoc tree

2016-07-04 10:47 GMT+02:00 Mark Brown <broonie@...nel.org>:
> On Mon, Jul 04, 2016 at 09:24:12AM +0200, Enric Balletbo Serra wrote:
>
>> I just saw that these patches and the others in the patch series were
>> not applied yet. As are fixes and were accepted since middle May, I
>
> No, they are actually applied like the e-mail said - please see my git.
>
>> expected see the patches merged in this release cycle, but we're at
>
> In general if you think a fix needs to go in urgently it's best to
> specifically identify this.  If nothing is specifically said and it's
> not obviously related to something done recently then the tendency will
> be to assume that the issue was recently introduced and is a fix for a
> development version.
>
>> rc6 so I suppose I'll need to wait to see them merged for 4.8 merge
>> window. Please can you coordinate with Heiko and make sure that these
>> patches were merged before he merges the patches to enable the audio
>> on Veyron? Otherwise we will break Veyron support for a while. I'd
>> really like have audio working on Veyron.
>
> As things stand they'll be merged in the next merge window.  They're
> buried in the middle of a branch with other things so I can't just send
> the branch as-is.  If these new patches you're talking about are going
> to get merged in the merge window as well so we're presumably mostly
> fine?

Yeah it's fine as long as the patches will be merged in next merge
window before the rockchip DTS updates.

It's only that I expected see them merged, but probably was only
something that I assumed wrongly.

Thanks,
 Enric