[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <X9HqLFwjHSPXqRgZ@kroah.com>
Date: Thu, 10 Dec 2020 10:28:12 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Chris Bloomfield <ginge264@...il.com>
Cc: devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Staging: ralink-gdma: ralink-gdma: Fix a blank line
coding style issue
On Thu, Dec 10, 2020 at 10:06:57AM +0000, Chris Bloomfield wrote:
> Fix a coding style issue as identified by checkpatch.pl
>
> Signed-off-by: Chris Bloomfield <ginge264@...il.com>
> ---
> drivers/staging/ralink-gdma/ralink-gdma.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/staging/ralink-gdma/ralink-gdma.c b/drivers/staging/ralink-gdma/ralink-gdma.c
> index 655df317d0ee..a6181a167814 100644
> --- 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;
>
With your knowledge of C, do you think the above change looks correct?
thanks,
greg k-h
Powered by blists - more mailing lists