From: Vitaly Mayatskih <v.mayatskih@gmail.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: Sanjay R Mehta <Sanju.Mehta@amd.com>,
gregkh@linuxfoundation.org, dan.j.williams@intel.com,
Thomas.Lendacky@amd.com, Shyam-sundar.S-k@amd.com,
Nehal-bakulchandra.Shah@amd.com, robh@kernel.org,
mchehab+samsung@kernel.org, davem@davemloft.net,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH v7 2/3] dmaengine: ptdma: register PTDMA controller as a DMA resource
Date: Tue, 24 Nov 2020 12:37:01 -0500 [thread overview]
Message-ID: <CAGF4SLiL8+=atY6A8M7tZUPOEeZfL61b0AucjeNoFfp8yGFfsQ@mail.gmail.com> (raw)
In-Reply-To: <20201124171813.GS8403@vkoul-mobl>
On Tue, Nov 24, 2020 at 12:18 PM Vinod Koul <vkoul@kernel.org> wrote:
> IIRC there were few issues that I would like to get fixed before we can
> apply.. I hope authors can reply to the comments received and we can
> discuss on this.
Sounds like a plan, thanks!
--
wbr, Vitaly
next prev parent reply other threads:[~2020-11-24 17:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 7:39 [PATCH v7 0/3] Add support for AMD PTDMA controller driver Sanjay R Mehta
2020-10-16 7:39 ` [PATCH v7 1/3] dmaengine: ptdma: Initial driver for the AMD PTDMA Sanjay R Mehta
2020-11-18 11:55 ` Vinod Koul
2021-03-18 10:46 ` Sanjay R Mehta
2021-03-22 6:04 ` Vinod Koul
2021-03-22 6:40 ` Sanjay R Mehta
2020-10-16 7:39 ` [PATCH v7 2/3] dmaengine: ptdma: register PTDMA controller as a DMA resource Sanjay R Mehta
2020-11-18 12:16 ` Vinod Koul
2020-11-24 14:23 ` Vitaly Mayatskih
2020-11-24 17:18 ` Vinod Koul
2020-11-24 17:37 ` Vitaly Mayatskih [this message]
2020-11-24 19:42 ` Sanjay R Mehta
2020-11-24 19:57 ` Sanjay R Mehta
2021-03-18 10:54 ` Sanjay R Mehta
2020-10-16 7:39 ` [PATCH v7 3/3] dmaengine: ptdma: Add debugfs entries for PTDMA information Sanjay R Mehta
2020-11-09 3:46 ` [PATCH v7 0/3] Add support for AMD PTDMA controller driver Sanjay R Mehta
2020-11-12 5:42 ` Sanjay R Mehta
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='CAGF4SLiL8+=atY6A8M7tZUPOEeZfL61b0AucjeNoFfp8yGFfsQ@mail.gmail.com' \
--to=v.mayatskih@gmail.com \
--cc=Nehal-bakulchandra.Shah@amd.com \
--cc=Sanju.Mehta@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).