On 12 September 2013 13:46, Srivatsa S. Bhat
wrote:
> Well, I felt having that line avoids clutter, especially since the code
> around it was already a bit hard to read..
Well, its exact opposite for me.. somehow my attending keeps dragging
to extra blank lines :)
> Anyway, I don't have any
On 09/12/2013 10:55 AM, Viresh Kumar wrote:
> We don't need a blank line just at start of a block, lets remove it.
>
Well, I felt having that line avoids clutter, especially since the code
around it was already a bit hard to read..
Anyway, I don't have any strong opinions either way. So no
On 09/12/2013 10:55 AM, Viresh Kumar wrote:
We don't need a blank line just at start of a block, lets remove it.
Well, I felt having that line avoids clutter, especially since the code
around it was already a bit hard to read..
Anyway, I don't have any strong opinions either way. So no
On 12 September 2013 13:46, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com wrote:
Well, I felt having that line avoids clutter, especially since the code
around it was already a bit hard to read..
Well, its exact opposite for me.. somehow my attending keeps dragging
to extra blank lines :)
We don't need a blank line just at start of a block, lets remove it.
Signed-off-by: Viresh Kumar
---
drivers/cpufreq/cpufreq.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 5a64f66..28477eb 100644
--- a/drivers/cpufreq/cpufreq.c
We don't need a blank line just at start of a block, lets remove it.
Signed-off-by: Viresh Kumar viresh.ku...@linaro.org
---
drivers/cpufreq/cpufreq.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 5a64f66..28477eb 100644
---
6 matches
Mail list logo
