From: Dan Carpenter <dan.carpenter@oracle.com>
To: Aakash Hemadri <aakashhemadri123@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] staging: ralink-gdma: Fix checkpatch.pl CHECK
Date: Wed, 10 Feb 2021 15:19:16 +0300 [thread overview]
Message-ID: <20210210121915.GX2696@kadam> (raw)
In-Reply-To: <20210210120348.262328-1-aakashhemadri123@gmail.com>
On Wed, Feb 10, 2021 at 05:33:48PM +0530, Aakash Hemadri wrote:
> Remove CHECK: Lines should not end with a '('
>
> Signed-off-by: Aakash Hemadri <aakashhemadri123@gmail.com>
> ---
>
> drivers/staging/ralink-gdma/ralink-gdma.c | 28 ++++++++++++-----------
> 1 file changed, 15 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/staging/ralink-gdma/ralink-gdma.c b/drivers/staging/ralink-gdma/ralink-gdma.c
> index 655df317d0ee..a11f915f3308 100644
> --- a/drivers/staging/ralink-gdma/ralink-gdma.c
> +++ b/drivers/staging/ralink-gdma/ralink-gdma.c
> @@ -135,8 +135,7 @@ struct gdma_data {
> int (*start_transfer)(struct gdma_dmaengine_chan *chan);
> };
>
> -static struct gdma_dma_dev *gdma_dma_chan_get_dev(
> - struct gdma_dmaengine_chan *chan)
> +static struct gdma_dma_dev *gdma_dma_chan_get_dev(struct gdma_dmaengine_chan *chan)
> {
> return container_of(chan->vchan.chan.device, struct gdma_dma_dev,
> ddev);
> @@ -510,10 +509,11 @@ static void gdma_dma_issue_pending(struct dma_chan *c)
> spin_unlock_irqrestore(&chan->vchan.lock, flags);
> }
>
> -static struct dma_async_tx_descriptor *gdma_dma_prep_slave_sg(
> - struct dma_chan *c, struct scatterlist *sgl,
> - unsigned int sg_len, enum dma_transfer_direction direction,
> - unsigned long flags, void *context)
> +static struct dma_async_tx_descriptor
> + *gdma_dma_prep_slave_sg(struct dma_chan *c, struct scatterlist *sgl,
Don't do it like this... The original code is better so, I guess, lets
leave it as is. There are two accepted ways to start a function in the
kernel:
ONE:
static type
function_name(paramenters)
TWO
static type function_name(paramenters)
Either option will let you grep for the names of the functions:
egrep "^[a-zA-Z]" dir/file.c | grep '('
regards,
dan carpenter
next prev parent reply other threads:[~2021-02-10 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 12:03 Aakash Hemadri
2021-02-10 12:07 ` Greg Kroah-Hartman
2021-02-10 12:19 ` Dan Carpenter [this message]
2021-02-10 12:35 ` Aakash Hemadri
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=20210210121915.GX2696@kadam \
--to=dan.carpenter@oracle.com \
--cc=aakashhemadri123@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®