[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c4ad08aeb9ed8e3f8bfaedc3e9e0df245d4a93a3.camel@perches.com>
Date: Thu, 24 Dec 2020 09:27:15 -0800
From: Joe Perches <joe@...ches.com>
To: Ayoub Soussi <ayoubfme@...il.com>, gregkh@...uxfoundation.org
Cc: devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: ralink-gdma: Fixed blank line coding style
issue
On Wed, 2020-12-23 at 21:22 +0100, Ayoub Soussi wrote:
> Fixed coding style issue.
[]
> diff --git a/drivers/staging/ralink-gdma/ralink-gdma.c b/drivers/staging/ralink-gdma/ralink-gdma.c
[]
> @@ -122,6 +122,7 @@ struct gdma_dma_dev {
> struct gdma_data *data;
> void __iomem *base;
> struct tasklet_struct task;
> +
> volatile unsigned long chan_issued;
> atomic_t cnt;
This is presumably a checkpatch false positive.
checkpatch is not now nor never will be a perfect tool.
Please consider what you are doing and what the desired coding style is
before submitting patches.
Powered by blists - more mailing lists