From: Vinod Koul <vkoul@kernel.org>
To: Radhey Shyam Pandey <radhey.shyam.pandey@amd.com>
Cc: michal.simek@xilinx.com, lars@metafoo.de, marex@denx.de,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
git@amd.com
Subject: Re: [PATCH 0/2] dmaengine: xilinx_dma: minor documentation updates
Date: Fri, 4 Nov 2022 19:54:29 +0530 [thread overview]
Message-ID: <Y2UgnelN3C/9nar3@matsya> (raw)
In-Reply-To: <1666683737-7668-1-git-send-email-radhey.shyam.pandey@amd.com>
On 25-10-22, 13:12, Radhey Shyam Pandey wrote:
> This patch series add missing kernel documentation for
> xilinx_dma_device_config() and also fix return doc
> for xilinx_dma_child_probe().
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2022-11-04 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 7:42 [PATCH 0/2] dmaengine: xilinx_dma: minor documentation updates Radhey Shyam Pandey
2022-10-25 7:42 ` [PATCH 1/2] dmaengine: xilinx_dma: fix xilinx_dma_child_probe() return documentation Radhey Shyam Pandey
2022-10-25 7:42 ` [PATCH 2/2] dmaengine: xilinx_dma : add xilinx_dma_device_config() " Radhey Shyam Pandey
2022-11-04 14:24 ` Vinod Koul [this message]
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=Y2UgnelN3C/9nar3@matsya \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=git@amd.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=michal.simek@xilinx.com \
--cc=radhey.shyam.pandey@amd.com \
/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