All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-arm-kernel@lists.infradead.org, linux-mmc@vger.kernel.org,
	Dan Williams <dan.j.williams@intel.com>,
	Volker Ernst <volker.ernst@txtr.com>,
	Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH 1/3] ARM: MXC: mxcmmc: misc cleanups
Date: Wed, 31 Mar 2010 15:02:00 +0200	[thread overview]
Message-ID: <20100331130200.GC30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <20100331123856.GW2241@pengutronix.de>

On Wed, Mar 31, 2010 at 02:38:56PM +0200, Sascha Hauer wrote:
> On Tue, Mar 30, 2010 at 08:31:59PM +0200, Daniel Mack wrote:
> > +			dev_err(mmc_dev(host->mmc),
> > +				"%s: read -ETIMEDOUT\n", __func__);
> >  			data->error = -ETIMEDOUT;
> >  		} else {
> > +			dev_err(mmc_dev(host->mmc), "%s: -EIO\n", __func__);
> 
> Do we really want to have these messages with dev_err? In the subject
> you are talking about debug output.

This _is_ definitely an error if get there, so I'll rather change the
commit message ;)

> 
> >  			data->error = -EIO;
> >  		}
> > -	} else {
> > +	} else
> >  		data->bytes_xfered = host->datasize;
> > -	}
> 
> Documentation/CodingStyle says that if braces are used in one branch of
> a conditional then they should be used in both branches.
> I personally don't care much about this statement but I think we should
> leave it as is. Otherwise some day someone wants to change it back
> according to the coding style.

Ok, true. I'll fix this (and the commit message) and resend.

Thanks,
Daniel

WARNING: multiple messages have this Message-ID (diff)
From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: MXC: mxcmmc: misc cleanups
Date: Wed, 31 Mar 2010 15:02:00 +0200	[thread overview]
Message-ID: <20100331130200.GC30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <20100331123856.GW2241@pengutronix.de>

On Wed, Mar 31, 2010 at 02:38:56PM +0200, Sascha Hauer wrote:
> On Tue, Mar 30, 2010 at 08:31:59PM +0200, Daniel Mack wrote:
> > +			dev_err(mmc_dev(host->mmc),
> > +				"%s: read -ETIMEDOUT\n", __func__);
> >  			data->error = -ETIMEDOUT;
> >  		} else {
> > +			dev_err(mmc_dev(host->mmc), "%s: -EIO\n", __func__);
> 
> Do we really want to have these messages with dev_err? In the subject
> you are talking about debug output.

This _is_ definitely an error if get there, so I'll rather change the
commit message ;)

> 
> >  			data->error = -EIO;
> >  		}
> > -	} else {
> > +	} else
> >  		data->bytes_xfered = host->datasize;
> > -	}
> 
> Documentation/CodingStyle says that if braces are used in one branch of
> a conditional then they should be used in both branches.
> I personally don't care much about this statement but I think we should
> leave it as is. Otherwise some day someone wants to change it back
> according to the coding style.

Ok, true. I'll fix this (and the commit message) and resend.

Thanks,
Daniel

  reply	other threads:[~2010-03-31 13:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-30 18:31 [PATCH 1/3] ARM: MXC: mxcmmc: misc cleanups Daniel Mack
2010-03-30 18:31 ` Daniel Mack
2010-03-30 18:32 ` [PATCH 2/3] ARM: MXC: mxcmmc: Teach the driver SDIO operations Daniel Mack
2010-03-30 18:32   ` Daniel Mack
2010-03-31 13:03   ` Sascha Hauer
2010-03-31 13:03     ` Sascha Hauer
2010-03-31 13:29     ` Daniel Mack
2010-03-31 13:29       ` Daniel Mack
2010-03-31 16:41       ` Michał Mirosław
2010-03-31 16:41         ` Michał Mirosław
2010-03-31 17:04         ` [PATCH] " Daniel Mack
2010-03-31 17:34           ` Michał Mirosław
2010-04-01  8:02             ` Daniel Mack
2010-03-30 18:32 ` [PATCH 3/3] ARM: MXC: mxcmmc: work around a bug in the SDHC busy line handling Daniel Mack
2010-03-30 18:32   ` Daniel Mack
2010-03-31 12:38 ` [PATCH 1/3] ARM: MXC: mxcmmc: misc cleanups Sascha Hauer
2010-03-31 12:38   ` Sascha Hauer
2010-03-31 13:02   ` Daniel Mack [this message]
2010-03-31 13:02     ` Daniel Mack
2010-03-31 13:35   ` [PATCH] " Daniel Mack
2010-03-31 13:17 ` [PATCH 1/3] " Julien Boibessot
  -- strict thread matches above, loose matches on Subject: below --
2010-04-01  8:03 Daniel Mack
2010-04-06 10:44 ` Daniel Mack
2010-04-08  9:34   ` Sascha Hauer
2010-04-08 10:59     ` Daniel Mack
2010-04-13 10:34     ` Daniel Mack
2010-04-14  7:21       ` Sascha Hauer
2010-04-14  8:11         ` Andy Green
2009-11-05 17:13 Patches for mxcmmc.c Daniel Mack
2009-11-05 17:13 ` [PATCH 1/3] ARM: MXC: mxcmmc: misc cleanups Daniel Mack

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=20100331130200.GC30801@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=dan.j.williams@intel.com \
    --cc=jkosina@suse.cz \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=volker.ernst@txtr.com \
    /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.