Re: [PATCH] i.MX Framebuffer: Cleanup Coding style
From: Sascha Hauer <s.hauer@pengutronix.de>
Date: 2008-08-21 07:06:37
On Wed, Aug 20, 2008 at 07:35:43PM +0200, Krzysztof Helt wrote:
quoted hunk ↗ jump to hunk
On Wed, 20 Aug 2008 18:15:21 +0200 Sascha Hauer [off-list ref] wrote:quoted
On Wed, Aug 20, 2008 at 05:35:01PM +0200, Krzysztof Helt wrote:quoted
On Tue, 19 Aug 2008 17:06:42 +0200 Sascha Hauer [off-list ref] wrote:quoted
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de> --- drivers/video/imxfb.c | 78 +++++++++++++++++++++++++------------------------ 1 files changed, 40 insertions(+), 38 deletions(-)I don't like some of the changes like wrapping lines which are not longer than 80 characters or removing alignment vs previous line because it contains spaces. There are also positive CS changes so not everything is bad.Hm, this patch only wraps lines longer than 80 characters (in one case it even merges two lines to one because it's still shorter than 80 chars).The change around line 250 wraps 80 chars line.@@ -250,7 +249,8 @@ imxfb_setcolreg(u_int regno, u_int red, u_int green, u_int blue, case FB_VISUAL_STATIC_PSEUDOCOLOR: case FB_VISUAL_PSEUDOCOLOR: - ret = imxfb_setpalettereg(regno, red, green, blue, trans, info); + ret = imxfb_setpalettereg(regno, red, green, blue, trans, + info);
Ok, you're right. I just saw my cursor blinking on position 81, but of course that means the line is 80 characters long. My bad
quoted hunk ↗ jump to hunk
break; }quoted
It also does not remove alignment vs the previous line, instead it aligns some lines against the previous line.@@ -185,7 +184,7 @@ static inline u_int chan_to_field(u_int chan, struct fb_bitfield *bf) static int imxfb_setpalettereg(u_int regno, u_int red, u_int green, u_int blue, - u_int trans, struct fb_info *info) + u_int trans, struct fb_info *info) { struct imxfb_info *fbi = info->par; u_int val, ret = 1;The removed line was previously aligned to start after the "(" in the previous line. One could move "static int" into the same line. You have added spaces between sizeof operator and the opening parenthesis. It is pointed out by the checkpatch script.
Ah, yes. This one I have copied from a Lindent run.
quoted
Maybe reading whitespace changes in patches is a bit confusing because the +/- at line starts mess it up.The changes I pointed above are ones I don't like. They are not bringing any benefit (nor better CS conformance nor readability). However, I recognize your patch does more positive changes then these pointed above. Also, my feelings toward some changes are my personal opinion and I won't block the patch you have posted. I would like to see the mentioned changes dropped but it is up to you.
I will rework it.
Regards,
Sascha
--
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hannoversche Str. 2, 31134 Hildesheim, Germany
Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/