DMA Engine development
 help / color / mirror / Atom feed
From: Basavaraj Natikar <bnatikar@amd.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
	Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Cc: vkoul@kernel.org, dmaengine@vger.kernel.org,
	Raju.Rangoju@amd.com, Frank.li@nxp.com, pstanner@redhat.com
Subject: Re: [PATCH v6 1/6] dmaengine: Move AMD DMA driver to separate directory
Date: Mon, 9 Sep 2024 23:05:26 +0530	[thread overview]
Message-ID: <d4a24e99-e1fe-4ab8-89f9-f13219160099@amd.com> (raw)
In-Reply-To: <20240909160049.GA531275@bhelgaas>


On 9/9/2024 9:30 PM, Bjorn Helgaas wrote:
> On Mon, Sep 09, 2024 at 06:09:36PM +0530, Basavaraj Natikar wrote:
>> Currently, AMD PTDMA driver is single DMA driver supported and newer AMD
>> platforms supports newer DMA engine. Hence move the current drivers to
>> separate directory. This would also mean the newer driver submissions to
>> AMD DMA driver in the future will also land in AMD specific directory.
> Since you're adding a second AMD DMA driver, the one-line git history
> will be more useful if you mention in the subject line that this patch
> moves the "PTDMA" driver specifically.

Sure, Bjorn. I will make the change in the next series, such as
"Moving the PTDMA driver to a separate AMD directory".

Thanks,
--
Basavaraj

>
> Bjorn


  reply	other threads:[~2024-09-09 17:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09 12:39 [PATCH v6 0/6] Add support of AMD AE4DMA DMA Engine Basavaraj Natikar
2024-09-09 12:39 ` [PATCH v6 1/6] dmaengine: Move AMD DMA driver to separate directory Basavaraj Natikar
2024-09-09 16:00   ` Bjorn Helgaas
2024-09-09 17:35     ` Basavaraj Natikar [this message]
2024-09-09 12:39 ` [PATCH v6 2/6] dmaengine: ae4dma: Add AMD ae4dma controller driver Basavaraj Natikar
2024-09-09 16:07   ` Bjorn Helgaas
2024-09-09 17:37     ` Basavaraj Natikar
2024-09-09 12:39 ` [PATCH v6 3/6] dmaengine: ptdma: Extend ptdma to support multi-channel and version Basavaraj Natikar
2024-09-09 12:39 ` [PATCH v6 4/6] dmaengine: ae4dma: Register AE4DMA using pt_dmaengine_register Basavaraj Natikar
2024-10-21 17:32   ` Vinod Koul
2024-10-22  5:23     ` Basavaraj Natikar
2024-10-23  6:09       ` Vinod Koul
2024-10-23 12:39         ` Basavaraj Natikar
2024-09-09 12:39 ` [PATCH v6 5/6] dmaengine: ptdma: Extend ptdma-debugfs to support multi-queue Basavaraj Natikar
2024-09-09 12:39 ` [PATCH v6 6/6] dmaengine: ae4dma: Register debugfs using ptdma_debugfs_setup Basavaraj Natikar

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=d4a24e99-e1fe-4ab8-89f9-f13219160099@amd.com \
    --to=bnatikar@amd.com \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=Frank.li@nxp.com \
    --cc=Raju.Rangoju@amd.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=helgaas@kernel.org \
    --cc=pstanner@redhat.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