[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <da042959-9c87-94cc-990c-27f7d9b8ab29@microchip.com>
Date: Mon, 7 Nov 2022 09:00:06 +0000
From: <Tudor.Ambarus@...rochip.com>
To: <vkoul@...nel.org>
CC: <peda@...ntia.se>, <du@...ntia.se>, <maciej.sosnowski@...el.com>,
<Nicolas.Ferre@...rochip.com>, <mripard@...nel.org>,
<torfl6749@...il.com>, <linux-kernel@...r.kernel.org>,
<dmaengine@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v2 00/32] dmaengine: at_hdmac: Fix concurrency bugs and
then convert to virt-dma
On 11/7/22 06:33, Vinod Koul wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 04-11-22, 23:29, Vinod Koul wrote:
>> On 04-11-22, 15:21, Tudor.Ambarus@...rochip.com wrote:
>>>
>>>>>
>>>>> This does not apply on dmaengine-fixes, can you please rebase and resend
>>>>>
>>>>
>>>> Sure, I can, but on my side it applies just fine, both on the fixes and next
>>>> branches. I used git://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git
>>>> Shall I use other tree?
>>
>> this is right tree, I was on fixes branch (for initial fixes) and i
>> think 7th or 8th one failed to apply for me...
>>
>>>
>>> $ git log --oneline
>>> 79029dc341c7 (HEAD, vkoul-dma/fixes) dmaengine: stm32-dma: fix potential race between pause and resume
>>>
>>> [cut]
>>>
>>> $ b4 am 20221025090306.297886-1-tudor.ambarus@...rochip.com
>>> Looking up https://lore.kernel.org/r/20221025090306.297886-1-tudor.ambarus%40microchip.com
>>> Grabbing thread from lore.kernel.org/all/20221025090306.297886-1-tudor.ambarus%40microchip.com/t.mbox.gz
>>> Analyzing 37 messages in the thread
>>> Checking attestation on all messages, may take a moment...
>
> Okay grabbing the b4 version did the trick, no sure why my local one
> failed. I have applied these now. Thanks
Cool, thank you!
Powered by blists - more mailing lists