From: Vinod Koul <vkoul@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
dmaengine@vger.kernel.org,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation: driver-api: fix dmatest.rst warning
Date: Mon, 11 Feb 2019 17:20:47 +0530 [thread overview]
Message-ID: <20190211115047.GQ4296@vkoul-mobl> (raw)
In-Reply-To: <da8b9103-5203-13da-65c5-232233ab0bfb@infradead.org>
On 10-02-19, 22:26, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix markup warning: insert a blank line before the hint.
>
> Documentation/driver-api/dmaengine/dmatest.rst:63: WARNING: Unexpected indentation.
Applied after adding dmaengine subsystem tag, thanks
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Cc: Vinod Koul <vkoul@kernel.org>
> Cc: dmaengine@vger.kernel.org
> ---
> Documentation/driver-api/dmaengine/dmatest.rst | 1 +
> 1 file changed, 1 insertion(+)
>
> --- lnx-50-rc6.orig/Documentation/driver-api/dmaengine/dmatest.rst
> +++ lnx-50-rc6/Documentation/driver-api/dmaengine/dmatest.rst
> @@ -59,6 +59,7 @@ parameter, that specific channel is requ
> is created with the existing parameters. This thread is set as pending
> and will be executed once run is set to 1. Any parameters set after the thread
> is created are not applied.
> +
> .. hint::
> available channel list could be extracted by running the following command::
>
>
--
~Vinod
prev parent reply other threads:[~2019-02-11 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 6:26 [PATCH] Documentation: driver-api: fix dmatest.rst warning Randy Dunlap
2019-02-11 10:29 ` Andy Shevchenko
2019-02-11 11:50 ` 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=20190211115047.GQ4296@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=corbet@lwn.net \
--cc=dmaengine@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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