public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: dmaengine@vger.kernel.org, open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv4 dmaengine 0/2] mv_xor: some devm cleanups
Date: Tue, 23 Dec 2025 16:37:37 +0530	[thread overview]
Message-ID: <aUp3-WM1DM2HQMFy@vaman> (raw)
In-Reply-To: <20251105210317.18215-1-rosenp@gmail.com>

On 05-11-25, 13:03, Rosen Penev wrote:
> Some devm cleanups that are now possible.
> 
> It's interesting that this driver lacks a _remove function to free its
> resources...
> 
> v2: resent with dmaengine prefix

Not required to add this in within []..
[PATCHv4 0/2] dmaengine: mv_xor..  would be fin

I cant apply this as it fails for me, please rebase

> v3: add error handling for devm_clk_get_optional_enabled to potentially
> handle EPROBE_DEFER.
> v4: remove request_irq based on feedback.
> 
> Rosen Penev (2):
>   dmaengine: mv_xor: use devm_platform_ioremap_resource
>   dmaengine: mv_xor: use devm_clk_get_optional_enabled
> 
>  drivers/dma/mv_xor.c | 34 +++++++++-------------------------
>  1 file changed, 9 insertions(+), 25 deletions(-)
> 
> --
> 2.51.2

-- 
~Vinod

      parent reply	other threads:[~2025-12-23 11:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 21:03 [PATCHv4 dmaengine 0/2] mv_xor: some devm cleanups Rosen Penev
2025-11-05 21:03 ` [PATCHv4 dmaengine 1/2] dmaengine: mv_xor: use devm_platform_ioremap_resource Rosen Penev
2025-11-05 21:03 ` [PATCHv4 dmaengine 2/2] dmaengine: mv_xor: use devm_clk_get_optional_enabled Rosen Penev
2025-12-23 11:07 ` Vinod Koul [this message]

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=aUp3-WM1DM2HQMFy@vaman \
    --to=vkoul@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rosenp@gmail.com \
    /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