dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Green Wan <green.wan@sifive.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: sf-pdma: fix kernel-doc W=1 warning
Date: Mon, 18 Nov 2019 16:16:33 +0800	[thread overview]
Message-ID: <CAJivOr4aHScXcvaHUJW0yj9Q6K73034_JxbWQQ2COd_mFBr8Cg@mail.gmail.com> (raw)
In-Reply-To: <20191118075821.GA82508@vkoul-mobl>

will fix the subject and split the patch. Thanks.

--
Green

On Mon, Nov 18, 2019 at 3:58 PM Vinod Koul <vkoul@kernel.org> wrote:
>
> On 15-11-19, 11:10, Green Wan wrote:
> > Fix kernel-doc W=1 warning. There are several comments starting from "/**"
> > but not for function comment purpose. Remove them to fix the warning.
> > Another definition in front of function causes warning. Move definition
> > to header file.
>
> We do not do these kind of titles for a patch, a patch should have
> subject which describes the changes and we do not mix multiple changes
> into a patch , so..
> >
> > kernel-doc warning:
> >
> > drivers/dma/sf-pdma/sf-pdma.c:28: warning: Function parameter or member
> >       'addr' not described in 'readq'
>
> 'describe redq parameter' can be good subject and a patch
>
> > drivers/dma/sf-pdma/sf-pdma.c:438: warning: Function parameter or member
> >       'ch' not described in 'SF_PDMA_REG_BASE'
> > drivers/dma/sf-pdma/sf-pdma.c:438: warning: Excess function parameter
> >       'pdma' description in 'SF_PDMA_REG_BASE'
>
> 'remove pdma description' can be second patch and subject
>
> >
> > Changes:
> >  - Replace string '/**' with '/*' not for comment purpose
> >  - Move definition, "SF_PDMA_REG_BASE", fomr sf-pdma.c to sf-pdma.h
> >
> > Signed-off-by: Green Wan <green.wan@sifive.com>
> > ---
> >  drivers/dma/sf-pdma/sf-pdma.c | 3 +--
> >  drivers/dma/sf-pdma/sf-pdma.h | 4 +++-
> >  2 files changed, 4 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/dma/sf-pdma/sf-pdma.c b/drivers/dma/sf-pdma/sf-pdma.c
> > index 16fe00553496..465256fe8b1f 100644
> > --- a/drivers/dma/sf-pdma/sf-pdma.c
> > +++ b/drivers/dma/sf-pdma/sf-pdma.c
> > @@ -1,5 +1,5 @@
> >  // SPDX-License-Identifier: GPL-2.0-or-later
> > -/**
> > +/*
> >   * SiFive FU540 Platform DMA driver
> >   * Copyright (C) 2019 SiFive
> >   *
> > @@ -435,7 +435,6 @@ static int sf_pdma_irq_init(struct platform_device *pdev, struct sf_pdma *pdma)
> >   *
> >   * Return: none
> >   */
> > -#define SF_PDMA_REG_BASE(ch) (pdma->membase + (PDMA_CHAN_OFFSET * (ch)))
> >  static void sf_pdma_setup_chans(struct sf_pdma *pdma)
> >  {
> >       int i;
> > diff --git a/drivers/dma/sf-pdma/sf-pdma.h b/drivers/dma/sf-pdma/sf-pdma.h
> > index 55816c9e0249..0c20167b097d 100644
> > --- a/drivers/dma/sf-pdma/sf-pdma.h
> > +++ b/drivers/dma/sf-pdma/sf-pdma.h
> > @@ -1,5 +1,5 @@
> >  /* SPDX-License-Identifier: GPL-2.0-or-later */
> > -/**
> > +/*
> >   * SiFive FU540 Platform DMA driver
> >   * Copyright (C) 2019 SiFive
> >   *
> > @@ -57,6 +57,8 @@
> >  /* Error Recovery */
> >  #define MAX_RETRY                                    1
> >
> > +#define SF_PDMA_REG_BASE(ch) (pdma->membase + (PDMA_CHAN_OFFSET * (ch)))
> > +
> >  struct pdma_regs {
> >       /* read-write regs */
> >       void __iomem *ctrl;             /* 4 bytes */
> >
> > base-commit: a7e335deed174a37fc6f84f69caaeff8a08f8ff8
> > --
> > 2.17.1
>
> --
> ~Vinod

      reply	other threads:[~2019-11-18  8:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15  3:10 [PATCH] dmaengine: sf-pdma: fix kernel-doc W=1 warning Green Wan
2019-11-18  7:58 ` Vinod Koul
2019-11-18  8:16   ` Green Wan [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=CAJivOr4aHScXcvaHUJW0yj9Q6K73034_JxbWQQ2COd_mFBr8Cg@mail.gmail.com \
    --to=green.wan@sifive.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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).