mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier.adi@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: cliffcai.sh@gmail.com, linux-mmc@vger.kernel.org,
	linux-kernel@vger.kernel.org, cliff.cai@analog.com,
	Bryan Wu <cooloney@kernel.org>
Subject: Re: [PATCH v4][mmc/host]:Blackfin SD Host Controller Driver
Date: Sun, 29 Nov 2009 16:39:16 -0500	[thread overview]
Message-ID: <8bd0f97a0911291339v7b0195dfjeb2065d011b47dc7@mail.gmail.com> (raw)
In-Reply-To: <20091125144307.5e7d6d6f.akpm@linux-foundation.org>

On Wed, Nov 25, 2009 at 17:43, Andrew Morton wrote:
> On Wed, 25 Nov 2009 17:25:20 -0500 Mike Frysinger wrote:
>> > Arguably wrong from a coding-style POV and looks weird IMO. __Adds a bit
>> > of risk that subsequent coders will think they're writing in python adn
>> > will add bugs.
>>
>> i dont really get what you're referring to here.  the code in question
>> looks ifne to me, and i dont see anything "python-esque" about it
>
> Code like
>
>        if (expr) {
>                line1;
>                line2;
>        } else
>                line3;
>
> looks odd and can cause people to later add bugs along the lines of
>
>        if (expr) {
>                line1;
>                line2;
>        } else
> +               line3a;
>                line3;
>
> this is particularly the case if line3 is long, or is preceded by a
> comment.  This has happened in the past.
>
> Adding the missing braces reduces the risk that this will occur.

*shrug* people can screw up braces regardless of how many statements
and/or branches there are.  i doubt people are going to get confused
and think kernel code is python, but if you really want to be pedantic
about braces, doesnt matter that much to me.
-mike

  reply	other threads:[~2009-11-29 21:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 15:19 cliffcai.sh
2009-11-25 22:04 ` Andrew Morton
2009-11-25 22:25   ` Mike Frysinger
2009-11-25 22:43     ` Andrew Morton
2009-11-29 21:39       ` Mike Frysinger [this message]
2009-12-04  2:08   ` Mike Frysinger

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=8bd0f97a0911291339v7b0195dfjeb2065d011b47dc7@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cliff.cai@analog.com \
    --cc=cliffcai.sh@gmail.com \
    --cc=cooloney@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®