[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150318112509.GP10964@mwanda>
Date: Wed, 18 Mar 2015 14:25:09 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Lorenzo Stoakes <lstoakes@...il.com>
Cc: Vitaly Kuznetsov <vkuznets@...hat.com>, devel@...verdev.osuosl.org,
linux-fbdev@...r.kernel.org,
Teddy Wang <teddy.wang@...iconmotion.com>,
Greg KH <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org,
Sudip Mukherjee <sudipm.mukherjee@...il.com>
Subject: Re: [PATCH RESEND 1/5] staging: sm750fb: Use memset_io instead of
memset
On Wed, Mar 18, 2015 at 11:12:20AM +0000, Lorenzo Stoakes wrote:
> On 18 March 2015 at 10:50, Vitaly Kuznetsov <vkuznets@...hat.com> wrote:
> > ERROR is reported by scripts/checkpatch.pl (spaces are missing after
> > ','). This coding style problem was there before your patch but I don't
> > think it makes sense to preserve it.
>
> [snip]
>
> > WARNING: please, no spaces at the start of a line
> > #137: FILE: drivers/staging/sm750fb/sm750.c:833:
>
> [snip]
>
> Hi Vitaly, these style issues have vexed me and I was not sure whether
> to make changes or preserve all the obvious errors so as not to blend
> the two changes inappropriately, however it does indeed make sense to
> fix these on the lines I'm changing, will fix these!
If it's a white space thing on the same line then it's generally ok to
fix it. The "one thing per patch" is meant to make patches easier to
review. If it's a trivial thing and it doesn't make it harder to review
then we are reasonable people.
Could you read your patches again and find other similar white space
issues.
+ void __iomem * pbuffer,*pstart;
Should be:
+ void __iomem *pbuffer, *pstart;
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists