On Fri, 2024-02-23 at 12:40 +0530, Vinod Koul wrote:
> On 22-02-24, 16:15, Nuno Sa wrote:
> > In axi_dmac_probe(), there's a mix in using device managed APIs and
> > explicitly cleaning things in the driver .remove() hook. Move to use
> > device managed APIs and thus drop the .remove() hook.
>
> This one fails for me somehow (applied on next after merging fixes with
> patch1 on fixes)
>
Oh really?
They do apply for me (unless I'm doing something wrong):
b4 shazam 20240222-axi-dmac-devm-probe-v3-0-16bdca9e64d6@xxxxxxxxxx
Grabbing thread from
lore.kernel.org/all/20240222-axi-dmac-devm-probe-v3-0-16bdca9e64d6@xxxxxxxxxx/t.
mbox.gz
Checking for newer revisions
Grabbing search results from lore.kernel.org
Analyzing 4 messages in the thread
Looking for additional code-review trailers on lore.kernel.org
Checking attestation on all messages, may take a moment...
---
✓ [PATCH v3 1/2] dmaengine: axi-dmac: fix possible race in remove()
✓ [PATCH v3 2/2] dmaengine: axi-dmac: move to device managed probe
---
✓ Signed: ed25519/nuno.sa@xxxxxxxxxx
✓ Signed: DKIM/analog.com
---
Total patches: 2
---
Base: using specified base-commit de7d9cb3b064fdfb2e0e7706d14ffee20b762ad2
Applying: dmaengine: axi-dmac: fix possible race in remove()
Applying: dmaengine: axi-dmac: move to device managed probe
I just applied them on top of dma-next. The tip is:
("dt-bindings: renesas,rcar-dmac: Add r8a779h0 support")
- Nuno Sá
