dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: dmaengine@vger.kernel.org, Hyun Kwon <hyun.kwon@xilinx.com>,
	Michal Simek <michal.simek@xilinx.com>
Subject: Re: [PATCH 3/3] dmaengine: xilinx: dpdma: fix kernel doc format
Date: Wed, 22 Jul 2020 20:24:35 +0530	[thread overview]
Message-ID: <20200722145435.GS12965@vkoul-mobl> (raw)
In-Reply-To: <20200722145127.GC29813@pendragon.ideasonboard.com>

On 22-07-20, 17:51, Laurent Pinchart wrote:

> > W=1 build again..
> 
> I get the same when plumbing the source file into the kerneldoc build.
> The generated documentation however contains the description of both
> desc.pending and desc.active. If you want to fix the warning, I think
> you should instead add a line to document @desc, but without removing
> the existing @desc.pending and @desc.active lines.

I would like to see clean build with W=1, helps to find other issues :)
So do feel free to send the patch to fix this, i will swap them..

-- 
~Vinod

  reply	other threads:[~2020-07-22 14:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-18 13:51 [PATCH 1/3] dmaengine: xilinx: dpdma: remove comparison of unsigned expression Vinod Koul
2020-07-18 13:52 ` [PATCH 2/3] dmaengine: xilinx: dpdma: add missing kernel doc Vinod Koul
2020-07-22 12:45   ` Laurent Pinchart
2020-07-18 13:52 ` [PATCH 3/3] dmaengine: xilinx: dpdma: fix kernel doc format Vinod Koul
2020-07-22 13:11   ` Laurent Pinchart
2020-07-22 14:26     ` Vinod Koul
2020-07-22 14:51       ` Laurent Pinchart
2020-07-22 14:54         ` Vinod Koul [this message]
2020-07-22 16:18           ` Laurent Pinchart
2020-07-22 12:44 ` [PATCH 1/3] dmaengine: xilinx: dpdma: remove comparison of unsigned expression Laurent Pinchart
2020-07-22 14:25   ` Vinod Koul

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=20200722145435.GS12965@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=hyun.kwon@xilinx.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=michal.simek@xilinx.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;
as well as URLs for NNTP newsgroup(s).