From: Dave Jiang <dave.jiang@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH v3 0/3] dmaengine: A little cleanup and refactoring
Date: Fri, 9 Jan 2026 14:07:41 -0700 [thread overview]
Message-ID: <2e143786-7a51-459f-8caf-5f3beefe0a18@intel.com> (raw)
In-Reply-To: <20260109173718.3605829-1-andriy.shevchenko@linux.intel.com>
On 1/9/26 10:35 AM, Andy Shevchenko wrote:
> This just a set of small almost ad-hoc cleanups and refactoring.
> Nothing special and nothing that changes behaviour.
>
> Changelog v3:
> - fixed checkpatch warning (mixed tabs and spaces) (Vinod)
>
> v2: 20251110085349.3414507-1-andriy.shevchenko@linux.intel.com
>
> Changelog v2:
> - dropped not very good (and not compilable) change (LKP)
>
> Andy Shevchenko (3):
> dmaengine: Refactor devm_dma_request_chan() for readability
> dmaengine: Use device_match_of_node() helper
> dmaengine: Sort headers alphabetically
>
> drivers/dma/dmaengine.c | 50 +++++++++++++++++++++--------------------
> 1 file changed, 26 insertions(+), 24 deletions(-)
>
for the series
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
next prev parent reply other threads:[~2026-01-09 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 17:35 Andy Shevchenko
2026-01-09 17:35 ` [PATCH v3 1/3] dmaengine: Refactor devm_dma_request_chan() for readability Andy Shevchenko
2026-01-09 17:35 ` [PATCH v3 2/3] dmaengine: Use device_match_of_node() helper Andy Shevchenko
2026-01-09 17:35 ` [PATCH v3 3/3] dmaengine: Sort headers alphabetically Andy Shevchenko
2026-01-09 21:07 ` Dave Jiang [this message]
2026-01-12 20:23 ` [PATCH v3 0/3] dmaengine: A little cleanup and refactoring Frank Li
2026-01-19 7:52 ` Andy Shevchenko
2026-02-25 11:24 ` 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=2e143786-7a51-459f-8caf-5f3beefe0a18@intel.com \
--to=dave.jiang@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome