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.
Re: [PATCH] staging: ralink-gdma: Fixed blank line coding style issue
On Wed, Dec 23, 2020 at 09:22:30PM +0100, Ayoub Soussi wrote: > Fixed coding style issue. > > Signed-off-by: Ayoub Soussi > --- > 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, does this change look correct? thanks, greg k-h
[PATCH] staging: ralink-gdma: Fixed blank line coding style issue
Fixed coding style issue. Signed-off-by: Ayoub Soussi --- 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; -- 2.17.1