All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] ASoC: Refector DAPM event handler
Date: Thu, 17 Jul 2008 14:48:06 +0100	[thread overview]
Message-ID: <20080717134756.GE15333@sirena.org.uk> (raw)
In-Reply-To: <s5habgghe74.wl%tiwai@suse.de>

On Thu, Jul 17, 2008 at 02:45:19PM +0200, Takashi Iwai wrote:

> With this patch, dapm_update_bits() is called even when
> power_change=0, so it changes the behavior.  You can check
> power_change only once and skip the rest via continue if it's false.

Fixed - dapm_update_bits() already suppresses duplicate writes.

> Also, better to put parentheses around bit-and operation.

Fixed.  As with some other things it might be worth adding checks you
want like this to checkpatch.

> Anyway, if the indent level really matters, you should better to put
> it as a function.

The new indentation level is fine - the major issue was that the old
layout was over 80 columns already (checkpatch!), plus the way it was
structured would lead to exploding nesting levels when new cases were
added.  Splitting it out would only move it away from the handling of
other widgets which wouldn't help so much.

I'll resubmit shortly.

  parent reply	other threads:[~2008-07-17 13:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 10:59 [PATCH 1/2] ASoC: Refector DAPM event handler Mark Brown
2008-07-17 10:59 ` [PATCH 2/2] ASoC: Factor PGA DAPM handling into main Mark Brown
2008-07-17 12:45 ` [PATCH 1/2] ASoC: Refector DAPM event handler Takashi Iwai
2008-07-17 12:53   ` Mark Brown
2008-07-17 13:07   ` Mark Brown
2008-07-17 13:17     ` Takashi Iwai
2008-07-17 13:25       ` Mark Brown
2008-07-17 13:48   ` Mark Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-17 14:06 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=20080717134756.GE15333@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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.