From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bracing the loop in kernel/softirq.c
Date: Thu, 21 Jun 2007 21:32:34 +0400 [thread overview]
Message-ID: <20070621173234.GA13057@cvg> (raw)
In-Reply-To: <9a8748490706211020g1d96bd2anc0caa0aa2fdc5045@mail.gmail.com>
[Jesper Juhl - Thu, Jun 21, 2007 at 07:20:33PM +0200]
| From: Jesper Juhl <jesper.juhl@gmail.com>
| To: Cyrill Gorcunov <gorcunov@gmail.com>
| Cc: LKML <linux-kernel@vger.kernel.org>
| Subject: Re: [PATCH] bracing the loop in kernel/softirq.c
| Date: Thu, 21 Jun 2007 19:20:33 +0200
|
> On 21/06/07, Cyrill Gorcunov <gorcunov@gmail.com> wrote:
>> [Jesper Juhl - Wed, Jun 20, 2007 at 11:01:44PM +0200]
>> | From: Jesper Juhl <jesper.juhl@gmail.com>
>> | To: Cyrill Gorcunov <gorcunov@gmail.com>
>> | Cc: LKML <linux-kernel@vger.kernel.org>
>> | Subject: Re: [PATCH] bracing the loop in kernel/softirq.c
>> | Date: Wed, 20 Jun 2007 23:01:44 +0200
>> |
>> > On 20/06/07, Cyrill Gorcunov <gorcunov@gmail.com> wrote:
>> >> This trivial patch adds braces over a one-line
>> >> loop. That makes code...well... little bit
>> >> convenient for (possible) further modifications.
>> >>
>> > That's generally not done.
>> >
>> > It's even in Documentation/CodingStyle :
>> >
>> > "
>> > Do not unnecessarily use braces where a single statement will do.
>> >
>> > if (condition)
>> > action();
>> > "
>>
>> look, the CodingStyle is absolutely right BUT:
>>
>> - dropping the braces are good solution for 'if' statement indeed
>> - dropping the braces are _not_ good for 'do' - 'while' loop 'case
>> it fails on further loop modifications. Moreover adding these
>> braces
>> we don't change amount of lines in code! So why souldn't we? I
>> don't
>> see any reason not to do.
>>
>
> Personally, in this case, I don't care. I'm simply telling you that
> usually that's not a patch that would get accepted, that's all. But
> it's all up to the maintainer of that area of the kernel (whom you
> probably want to at least Cc in addition to just LKML). :-)
>
> --
> Jesper Juhl <jesper.juhl@gmail.com>
> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
> Plain text mails only, please http://www.expita.com/nomime.html
>
Anyway, thanks for comments ;)
Cyrill
next prev parent reply other threads:[~2007-06-21 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 17:57 [PATCH] bracing the loop in kernel/softirq.c Cyrill Gorcunov
2007-06-20 21:01 ` Jesper Juhl
2007-06-21 13:49 ` Cyrill Gorcunov
2007-06-21 17:20 ` Jesper Juhl
2007-06-21 17:32 ` Cyrill Gorcunov [this message]
2007-06-21 18:52 ` Jeremy Fitzhardinge
2007-06-21 19:11 ` Cyrill Gorcunov
2007-06-22 15:54 ` Cyrill Gorcunov
2007-06-22 18:05 ` Jeremy Fitzhardinge
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=20070621173234.GA13057@cvg \
--to=gorcunov@gmail.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@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.