All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, lrg@ti.com
Subject: Re: [PATCH 1/3] ASoC: support sample sizes properly in the WM8776 codec driver
Date: Thu, 15 Sep 2011 10:16:20 -0500	[thread overview]
Message-ID: <4E7216C4.1090902@freescale.com> (raw)
In-Reply-To: <20110915132154.GF7988@opensource.wolfsonmicro.com>

Mark Brown wrote:
> On Tue, Sep 13, 2011 at 12:59:35PM -0500, Timur Tabi wrote:
> 
>> -	iface = 0;
>> -
> 
> Random stylistic changes like this make review harder, especially when
> they're not mentioned in the changelog. 

This is not a random stylistic change.  My patch changes the way iface is
calculated.  Therefore, removing an unnecessary pre-initialization of iface is
both obvious and expected.

The "iface = 0" line is used in the original code because the driver did not
have a "default" case for the "switch" statement.  Since I added a default case,
there was no need to pre-initialize iface anymore.

If I had left that line in the driver, someone would have complained that I'm
pre-initializing iface unnecessarily.

> In this case it's not clear
> from the diff alone that there are no other places where iface gets
> written to

Ok, so that means that you need to look at the original code in order to
understand the change completely.  What's wrong with that?  I just don't see how
this is a valid criticism for any patch.

> An important aspect of review is checking that the change being made
> actually do what they're supposed to do, unexpected additional stuff is
> a red flag - you have to work out if it's something the sender meant to
> include, what it's supposed to do and if it's a good idea.

Again, I just don't understand this complaint of my patch.  I've carefully read
your email, and I re-examined my patch and the original code, and I still don't
think that there's anything wrong with the patch.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2011-09-15 15:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13 17:59 [PATCH 1/3] ASoC: support sample sizes properly in the WM8776 codec driver Timur Tabi
2011-09-13 17:59 ` [PATCH 2/3] ASoC: support all possible sample rates in the WM8776 driver Timur Tabi
2011-09-14 12:36   ` Liam Girdwood
2011-09-15 10:24   ` Mark Brown
2011-09-15 15:08     ` Timur Tabi
2011-09-15 22:38       ` Mark Brown
2011-09-15 23:06         ` Tabi Timur-B04825
2011-09-15 23:49           ` Mark Brown
2011-09-16 13:48             ` Timur Tabi
2011-09-17 13:04               ` Mark Brown
2011-09-13 17:59 ` [PATCH 3/3] ASoC: improve asynchronous mode support in the fsl_ssi driver Timur Tabi
2011-09-14 12:37   ` Liam Girdwood
2011-09-15 23:06   ` Mark Brown
2011-09-15 23:49   ` Mark Brown
2011-09-14 12:35 ` [PATCH 1/3] ASoC: support sample sizes properly in the WM8776 codec driver Liam Girdwood
2011-09-14 21:51   ` Timur Tabi
2011-09-15 10:26     ` Mark Brown
2011-09-15 11:28       ` Tabi Timur-B04825
2011-09-15 13:21 ` Mark Brown
2011-09-15 15:16   ` Timur Tabi [this message]
2011-09-15 23:38     ` Mark Brown
2011-09-16  9:07 ` Mark Brown

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=4E7216C4.1090902@freescale.com \
    --to=timur@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@ti.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.