All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Vinod Koul <vkoul@kernel.org>
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 19:18:17 +0300	[thread overview]
Message-ID: <20200722161817.GM29813@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20200722145435.GS12965@vkoul-mobl>

On Wed, Jul 22, 2020 at 08:24:35PM +0530, Vinod Koul wrote:
> 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..

Done, see "[PATCH] dmaengine: xilinx: dpdma: Fix kerneldoc warning".

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2020-07-22 16:18 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
2020-07-22 16:18           ` Laurent Pinchart [this message]
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=20200722161817.GM29813@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=hyun.kwon@xilinx.com \
    --cc=michal.simek@xilinx.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.