From: Vinod Koul <vinod.koul@intel.com>
To: "Stefan Brüns" <stefan.bruens@rwth-aachen.de>
Cc: dmaengine@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] dmaengine: Correct some documentation
Date: Thu, 21 Sep 2017 22:36:15 +0530 [thread overview]
Message-ID: <20170921170615.GD30097@localhost> (raw)
In-Reply-To: <20170911234445.30831-1-stefan.bruens@rwth-aachen.de>
On Tue, Sep 12, 2017 at 01:44:43AM +0200, Stefan Brüns wrote:
> Some small fixes for dmaengine documentation.
Applied, thanks
>
> Stefan Brüns (2):
> dmaengine: List all allowed values for src/dst_addr_width in kernel
> doc
> dmaengine: Mark struct dma_slave_caps kernel-doc correctly, clarify
>
> include/linux/dmaengine.h | 30 +++++++++++++++++-------------
> 1 file changed, 17 insertions(+), 13 deletions(-)
>
> --
> 2.14.1
>
--
~Vinod
prev parent reply other threads:[~2017-09-21 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 23:44 [PATCH 0/2] dmaengine: Correct some documentation Stefan Brüns
2017-09-11 23:44 ` [PATCH 1/2] dmaengine: List all allowed values for src/dst_addr_width in kernel doc Stefan Brüns
2017-09-11 23:44 ` [PATCH 2/2] dmaengine: Mark struct dma_slave_caps kernel-doc correctly, clarify Stefan Brüns
2017-09-21 17:06 ` 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=20170921170615.GD30097@localhost \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan.bruens@rwth-aachen.de \
/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