Re: [PATCH][2.5] Double quote patches part one: drivers 1/2

From: Russell King (
Date: Tue Jun 11 2002 - 05:43:44 EST

On Tue, Jun 11, 2002 at 04:24:01AM -0600, Thunder from the hill wrote:
> On Tue, 11 Jun 2002, Russell King wrote:
> > 1. Spaces -> source bloat.
> No spaces -> looks unsatisfying, someone mentioned.

Authors taste.

> > 2. No tab at the start of the file -> yuck when reading the ASM.
> What do you mean by that?

Ever tried:

make kernel/fork.s

and then read kernel/fork.s ? Yes, some people who care about getting
the best out of the kernel do convert C to assembly and then read the
result. If there's something really yucky in there, then you go back
and fix it in the C source.

> > My preferred way of fixing these in ARM stuff is to add <tab><tab><tab>\n\
> > to each line (with the appropriate number of tabs. See
> > arch/arm/kernel/semaphore.c for an example.
> Hmm... Wasn't that the behavior we wanted to fix with the concatenated
> strings?

"behaviour" or "style". I prefer my style for the code I maintain, which
is close to Linus' style. There is no current style for fixing gcc 3.x
stuff, so its up to the authors of the code to set the style. I've
decided on one which matches the style of my multi-line macros for
consistency sake. I'd rather not invent another style for multi-line

Sure, both "fix" the underlying problem. But how readable is it in the

BTW, your sig is being messed up by the mixture of spaces and tabs:

> German attitude becoming | Thunder from the hill at ngforever
> rightaway popular: |
> "Get outa my way, | free inhabitant not directly
> for I got a mobile phone!" | belonging anywhere

Russell King (                The developer of ARM Linux

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to More majordomo info at Please read the FAQ at

This archive was generated by hypermail 2b29 : Sat Jun 15 2002 - 22:00:22 EST