alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>,
	Misael Lopez Cruz <misael.lopez@ti.com>
Subject: Re: [PATCH 01/10] ASoC: twl6040: Rename pga_event to out_drv_event
Date: Tue, 27 Sep 2011 09:17:29 +0300	[thread overview]
Message-ID: <2328247.bSzubebQHV@barack> (raw)
In-Reply-To: <20110926211956.GA2872@opensource.wolfsonmicro.com>

On Monday 26 September 2011 22:19:57 Mark Brown wrote:
> On Mon, Sep 26, 2011 at 04:26:24PM +0300, Peter Ujfalusi wrote:
> > This event handler is used with the OUT_DRV widgets.
> > The name pga_event was misleading.
> 
> Applied, though
> 
> > index d5c4bb4..b63ee24 100644
> > --- a/sound/soc/codecs/twl6040.c
> > +++ b/sound/soc/codecs/twl6040.c
> > @@ -72,7 +72,6 @@ struct twl6040_output {
> > 
> >  	u16 right_step;
> >  	unsigned int step_delay;
> >  	u16 ramp;
> > 
> > -	u16 mute;
> > 
> >  	struct completion ramp_done;
> >  
> >  };
> 
> This appears to be a random unrelated change.

Argh, this supposed to be a separate commit, it got squashed accidentally, 
sorry.

--
Péter

  reply	other threads:[~2011-09-27  6:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-26 13:26 [PATCH 00/10] ASoC: twl6040: Gain ramp code cleanups Peter Ujfalusi
2011-09-26 13:26 ` [PATCH 01/10] ASoC: twl6040: Rename pga_event to out_drv_event Peter Ujfalusi
2011-09-26 21:19   ` Mark Brown
2011-09-27  6:17     ` Péter Ujfalusi [this message]
2011-09-26 13:26 ` [PATCH 02/10] ASoC: twl6040: Combine the custom volsw get, and put functions Peter Ujfalusi
2011-09-26 21:21   ` Mark Brown
2011-09-27  6:16     ` Péter Ujfalusi
2011-09-27 10:56       ` Mark Brown
2011-09-27 11:21         ` Péter Ujfalusi
2011-09-27 11:42           ` Mark Brown
2011-09-27 12:55             ` Péter Ujfalusi
2011-09-26 13:26 ` [PATCH 03/10] ASoC: twl6040: Move delayed_work struct inside twl6040_output for HS/HF Peter Ujfalusi
2011-09-26 21:23   ` Mark Brown
2011-09-26 13:26 ` [PATCH 04/10] ASoC: twl6040: Move the delayed_work for HS detection under twl6040_jack_data Peter Ujfalusi
2011-09-26 21:24   ` Mark Brown
2011-09-26 13:26 ` [PATCH 05/10] ASoC: twl6040: One workqueue should be enough Peter Ujfalusi
2011-09-26 14:41   ` Mark Brown
2011-09-26 17:20     ` Ujfalusi, Peter
2011-09-26 21:29       ` Mark Brown
2011-09-27  6:33         ` Péter Ujfalusi
2011-09-26 13:26 ` [PATCH 06/10] ASoC: twl6040: correct loop counters for HS/HF ramp code Peter Ujfalusi
2011-09-26 21:33   ` Mark Brown
2011-09-27  6:21     ` Péter Ujfalusi
2011-09-27 11:12       ` Mark Brown
2011-09-26 13:26 ` [PATCH 07/10] ASoC: twl6040: No need to change delay during HS ramp Peter Ujfalusi
2011-09-26 21:33   ` Mark Brown
2011-09-26 13:26 ` [PATCH 08/10] ASoC: twl6040: No need to change delay during HF ramp Peter Ujfalusi
2011-09-26 21:33   ` Mark Brown
2011-09-26 13:26 ` [PATCH 09/10] ASoC: twl6040: Shift 2 identifies the HS output in out_drv_event Peter Ujfalusi
2011-09-26 13:26 ` [PATCH 10/10] ASoC: twl6040: Simplify code in out_drv_event for pending work check Peter Ujfalusi
2011-09-26 14:30   ` Mark Brown
2011-09-26 17:27     ` Ujfalusi, Peter

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=2328247.bSzubebQHV@barack \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@ti.com \
    --cc=misael.lopez@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).