DMA Engine development
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: Vinod Koul <vkoul@kernel.org>, Nuno Sa <nuno.sa@analog.com>
Cc: dmaengine@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v3 2/2] dmaengine: axi-dmac: move to device managed probe
Date: Fri, 23 Feb 2024 10:07:42 +0100	[thread overview]
Message-ID: <b7a24cc765268fb425d528cd036fc8a27806649a.camel@gmail.com> (raw)
In-Reply-To: <ZdhE2m40lsxIgdr7@matsya>

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@analog.com
Grabbing thread from
lore.kernel.org/all/20240222-axi-dmac-devm-probe-v3-0-16bdca9e64d6@analog.com/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@analog.com
  ✓ 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á

  reply	other threads:[~2024-02-23  9:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 15:15 [PATCH v3 0/2] dmaengine: axi-dmac: move to device managed probe Nuno Sa
2024-02-22 15:15 ` [PATCH v3 1/2] dmaengine: axi-dmac: fix possible race in remove() Nuno Sa
2024-02-22 15:15 ` [PATCH v3 2/2] dmaengine: axi-dmac: move to device managed probe Nuno Sa
2024-02-23  7:10   ` Vinod Koul
2024-02-23  9:07     ` Nuno Sá [this message]
2024-04-07 16:38 ` (subset) [PATCH v3 0/2] " Vinod Koul

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b7a24cc765268fb425d528cd036fc8a27806649a.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=lars@metafoo.de \
    --cc=nuno.sa@analog.com \
    --cc=vkoul@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox