public inbox for dmaengine@vger.kernel.org
 help / color / mirror / Atom feed
From: Basavaraj Natikar <bnatikar@amd.com>
To: Vinod Koul <vkoul@kernel.org>,
	Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Cc: dmaengine@vger.kernel.org, Raju.Rangoju@amd.com,
	Frank.li@nxp.com, helgaas@kernel.org, pstanner@redhat.com
Subject: Re: [PATCH v5 3/7] dmaengine: ptdma: Move common functions to common code
Date: Mon, 2 Sep 2024 12:37:41 +0530	[thread overview]
Message-ID: <9a813b70-4e24-4001-af4f-cbcf92582cb0@amd.com> (raw)
In-Reply-To: <Zs8jpVrnBuyr/wiQ@vaman>


On 8/28/2024 6:48 PM, Vinod Koul wrote:
> On 08-07-24, 20:14, Basavaraj Natikar wrote:
>> To focus on reusability of ptdma code across modules extract common
>> functions into reusable modules.
>>
>> Reviewed-by: Raju Rangoju <Raju.Rangoju@amd.com>
>> Signed-off-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
>> ---
>>  MAINTAINERS                             | 1 +
>>  drivers/dma/amd/ptdma/ptdma-dev.c       | 2 +-
>>  drivers/dma/amd/ptdma/ptdma-dmaengine.c | 3 +--
>>  3 files changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 539bf52410de..97d97ddf26f5 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -952,6 +952,7 @@ M:	Basavaraj Natikar <Basavaraj.Natikar@amd.com>
>>  L:	dmaengine@vger.kernel.org
>>  S:	Maintained
>>  F:	drivers/dma/amd/ae4dma/
>> +F:	drivers/dma/amd/common/
> I think this should be made amd/ to avoid churn when a file is
> added/dropped

Sure, I will remove the common directory and include everything
in the C files.

>
>>  
>>  AMD AXI W1 DRIVER
>>  M:	Kris Chaplin <kris.chaplin@amd.com>
>> diff --git a/drivers/dma/amd/ptdma/ptdma-dev.c b/drivers/dma/amd/ptdma/ptdma-dev.c
>> index a2bf13ff18b6..2bdf418fe556 100644
>> --- a/drivers/dma/amd/ptdma/ptdma-dev.c
>> +++ b/drivers/dma/amd/ptdma/ptdma-dev.c
>> @@ -17,7 +17,7 @@
>>  #include <linux/module.h>
>>  #include <linux/pci.h>
>>  
>> -#include "ptdma.h"
>> +#include "../common/amd_dma.h"
>>  
>>  /* Human-readable error strings */
>>  static char *pt_error_codes[] = {
>> diff --git a/drivers/dma/amd/ptdma/ptdma-dmaengine.c b/drivers/dma/amd/ptdma/ptdma-dmaengine.c
>> index a2e7c2cec15e..66ea10499643 100644
>> --- a/drivers/dma/amd/ptdma/ptdma-dmaengine.c
>> +++ b/drivers/dma/amd/ptdma/ptdma-dmaengine.c
>> @@ -9,8 +9,7 @@
>>   * Author: Gary R Hook <gary.hook@amd.com>
>>   */
>>  
>> -#include "ptdma.h"
>> -#include "../../dmaengine.h"
>> +#include "../common/amd_dma.h"
> So the driver was including old headers and now new, but I dont see any
> functions being moved? Does each patch compile...?

Yes, this compiles. As mentioned in the previous comment, I will remove
the common directory and include everything in the C files.


Thanks,
--
Basavaraj

>


  reply	other threads:[~2024-09-02  7:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08 14:44 [PATCH v5 0/7] Add support of AMD AE4DMA DMA Engine Basavaraj Natikar
2024-07-08 14:44 ` [PATCH v5 1/7] dmaengine: Move AMD DMA driver to separate directory Basavaraj Natikar
2024-07-08 14:44 ` [PATCH v5 2/7] dmaengine: ae4dma: Add AMD ae4dma controller driver Basavaraj Natikar
2024-08-28 13:23   ` Vinod Koul
2024-09-02  6:47     ` Basavaraj Natikar
2024-07-08 14:44 ` [PATCH v5 3/7] dmaengine: ptdma: Move common functions to common code Basavaraj Natikar
2024-08-28 13:18   ` Vinod Koul
2024-09-02  7:07     ` Basavaraj Natikar [this message]
2024-07-08 14:44 ` [PATCH v5 4/7] dmaengine: ptdma: Extend ptdma to support multi-channel and version Basavaraj Natikar
2024-08-28 17:46   ` Vinod Koul
2024-09-02  7:01     ` Basavaraj Natikar
2024-07-08 14:44 ` [PATCH v5 5/7] dmaengine: ae4dma: Register AE4DMA using pt_dmaengine_register Basavaraj Natikar
2024-07-08 14:44 ` [PATCH v5 6/7] dmaengine: ptdma: Extend ptdma-debugfs to support multi-queue Basavaraj Natikar
2024-07-08 14:45 ` [PATCH v5 7/7] 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=9a813b70-4e24-4001-af4f-cbcf92582cb0@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