From: Lizhi Hou <lizhi.hou@amd.com>
To: Tadeusz Struk <tstruk@gigaio.com>, <vkoul@kernel.org>,
<dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <nishads@amd.com>, <sonal.santan@amd.com>, <max.zhen@amd.com>
Subject: Re: [PATCH V9 1/2] dmaengine: amd: Add empty Kconfig and Makefile for AMD drivers
Date: Tue, 5 Mar 2024 13:48:09 -0800 [thread overview]
Message-ID: <b3200804-b00f-b0dc-f6eb-28e87e8aa157@amd.com> (raw)
In-Reply-To: <1a2f36bd-4913-401a-84cd-c3f77725fbaf@gigaio.com>
On 3/5/24 01:16, Tadeusz Struk wrote:
> On 2/27/24 18:08, Lizhi Hou wrote:
>> Add amd/ for AMD dmaengine drivers. Create empty Kconfig and Makefile
>> underneath.
>>
>> Signed-off-by: Lizhi Hou<lizhi.hou@amd.com>
>> ---
>> drivers/dma/Kconfig | 2 ++
>> drivers/dma/Makefile | 1 +
>> drivers/dma/amd/Kconfig | 1 +
>> drivers/dma/amd/Makefile | 4 ++++
>> 4 files changed, 8 insertions(+)
>> create mode 100644 drivers/dma/amd/Kconfig
>> create mode 100644 drivers/dma/amd/Makefile
>
> Hi Lizhi,
> I think you may want to change the order of the patches.
> Adding the Kconfig and Makefile changes in the first patch,
> and the code itself in the second patch will hurt git bisect.
> Just swap them around.
This patch was introduced for another AMD driver ae4dma patchset.
It looks ae4dma plan has changed.
I am going to merge this 2 patches into 1 patch.
Thanks,
Lizhi
> --
> Regards,
> Tadeusz
next prev parent reply other threads:[~2024-03-05 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 17:08 [PATCH V9 0/2] AMD QDMA driver Lizhi Hou
2024-02-27 17:08 ` [PATCH V9 1/2] dmaengine: amd: Add empty Kconfig and Makefile for AMD drivers Lizhi Hou
2024-03-05 9:16 ` Tadeusz Struk
2024-03-05 21:48 ` Lizhi Hou [this message]
2024-02-27 17:08 ` [PATCH V9 2/2] dmaengine: amd: qdma: Add AMD QDMA driver Lizhi Hou
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=b3200804-b00f-b0dc-f6eb-28e87e8aa157@amd.com \
--to=lizhi.hou@amd.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max.zhen@amd.com \
--cc=nishads@amd.com \
--cc=sonal.santan@amd.com \
--cc=tstruk@gigaio.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
all inboxes | Powered by JetHome®