From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: kernel-janitors@vger.kernel.org
Subject: Re: switch identation was: Re: [Kernel-janitors] [PATCH] Fix warning
Date: Thu, 08 Jan 2004 20:13:45 +0000 [thread overview]
Message-ID: <20040108201345.GX3062@conectiva.com.br> (raw)
In-Reply-To: <20040107164516.50bcd936.rddunlap@osdl.org>
Em Thu, Jan 08, 2004 at 11:40:04AM -0800, Randy.Dunlap escreveu:
> On Thu, 08 Jan 2004 05:36:20 -0200 Luiz Fernando Capitulino <lcapitulino@prefeitura.sp.gov.br> wrote:
>
> |
> | Hi Randy,
> |
> | Em Qua, 2004-01-07 às 22:45, Randy.Dunlap escreveu:
> |
> | > | >> Should I rediff ?
> | >
> | > No. But that
> | > + if(! pdev_is_sata(dev)) {
> | > is really ugly (the spacing in "if(! " part of it).
> | >
> | > And all this warning needs to fix it is an additional semi-colon, like:
> | >
> | > -sata_skip:
> | > +sata_skip:;
> | >
> | > although I don't disapprove of the intent of your patch.
> |
> | So, I will rediff only for the "if(! ". Ok ?
>
> OK, I'll merge that, except that if and switch are not functions,
> so we usually put a space after them and before the opening '('
> [yes, I'm slightly disagreeing with acme's proposed switch formatting].
not at all, if I proposed something like:
switch(foo) {
.
.
.
I'd be nuts 8)
switch (foo) {
case bar:
__bar();
break;
case baz:
__baz();
break;
default:
printk(KERN_ERR "whatever\n");
break;
}
Is how I write my code and fix other's :)
- Arnaldo
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2004-01-08 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 0:45 switch identation was: Re: [Kernel-janitors] [PATCH] Fix Randy.Dunlap
2004-01-08 7:36 ` Luiz Fernando Capitulino
2004-01-08 19:40 ` Randy.Dunlap
2004-01-08 20:13 ` Arnaldo Carvalho de Melo [this message]
2004-01-08 20:19 ` switch identation was: Re: [Kernel-janitors] [PATCH] Fix warning Arnaldo Carvalho de Melo
2004-01-09 12:26 ` switch identation was: Re: [Kernel-janitors] [PATCH] Fix Luiz Fernando Capitulino
2004-01-12 3:32 ` Randy.Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040108201345.GX3062@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.