linux-kernel - Re: [PATCH v3 00/14] ARM: pxa: switch to DMA slave maps

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]

Date:   Wed, 27 Jun 2018 23:03:16 +0200
From:   Daniel Mack <daniel@...que.org>
To:     Robert Jarzmik <robert.jarzmik@...e.fr>,
        Mark Brown <broonie@...nel.org>
Cc:     Boris Brezillon <boris.brezillon@...tlin.com>,
        linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org,
        alsa-devel@...a-project.org
Subject: Re: [PATCH v3 00/14] ARM: pxa: switch to DMA slave maps

On Wednesday, June 27, 2018 05:11 PM, Robert Jarzmik wrote:
> Mark Brown <broonie@...nel.org> writes:
> 
>> On Mon, Jun 18, 2018 at 09:56:20PM +0200, Robert Jarzmik wrote:
>>
>>> I must insist on "Wednesday", as I need to have one last pass from 0-day kernel
>>> checker to be fully covered, and I'd like as well to know which tree the ASoC
>>> patch will take, ie. if Mark commits to take it, or rather wants to pull from
>>> the imutable branch.
>>
>> I'll pull the branch in (a signed tag would've been nicer but it's not
>> the end of the world).
> Yeah, I realised that too ... late.
> 
> Anyways, the immutable branch doesn't contain the specific ASoC patch "ASoC:
> pxa: remove the dmaengine compat need", and up to my better understanding
> neither does your for-next branch.
> 
> So until I see it in your branch it will dwelve happily in pxa/for-next. If it
> has to be routed through your tree, so that Daniel can work on ASoC pxa, I'd
> like to know at -rc4 time so that I drop it from my pxa/for-next branch.

Ah, yes. The series I just posted depends on that.