From: Markus Elfring <Markus.Elfring@web.de>
To: Rosen Penev <rosenp@gmail.com>,
dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Frank Li <Frank.Li@kernel.org>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH v3] dmaengine: at_hdmac: use devm APIs in probe()
Date: Thu, 20 Aug 2026 15:32:21 +0200 [thread overview]
Message-ID: <f2beef49-1eff-466f-bbf8-2d701ade2f54@web.de> (raw)
In-Reply-To: <20260817201200.10952-1-rosenp@gmail.com>
…
> Simplify the error handling path and removes explicit cleanup code.
remove?
Would it be helpful to mention at_dma_probe() in the summary phrase?
Regards,
Markus
next prev parent reply other threads:[~2026-08-20 13:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 20:12 [PATCHv3] dmaengine: at_hdmac: use devm APIs in probe() Rosen Penev
2026-08-17 21:37 ` Frank Li
2026-08-20 13:32 ` Markus Elfring [this message]
2026-08-20 15:12 ` Frank Li
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=f2beef49-1eff-466f-bbf8-2d701ade2f54@web.de \
--to=markus.elfring@web.de \
--cc=Frank.Li@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=rosenp@gmail.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