Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, subhransu.s.prusty@intel.com,
	lgirdwood@gmail.com
Subject: Re: [PATCH v4 3/7] ASoC: Intel: sst - add pcm ops handling
Date: Fri, 17 Oct 2014 17:05:23 +0530	[thread overview]
Message-ID: <20141017113523.GR1638@intel.com> (raw)
In-Reply-To: <20141017120710.GG1820@sirena.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1013 bytes --]

On Fri, Oct 17, 2014 at 02:07:10PM +0200, Mark Brown wrote:
> On Thu, Oct 16, 2014 at 08:00:15PM +0530, Vinod Koul wrote:
> 
> > +int free_stream_context(struct intel_sst_drv *ctx, unsigned int str_id)
> > +{
> > +	struct stream_info *stream;
> > +	int ret = 0;
> > +
> > +	stream = get_stream_info(ctx, str_id);
> > +	if (stream) {
> > +		/* str_id is valid, so stream is alloacted */
> > +		ret = sst_free_stream(ctx, str_id);
> > +		if (ret)
> > +			sst_clean_stream(&ctx->streams[str_id]);
> > +		return ret;
> > +	}
> > +	return ret;
> > +}
> 
> I keep on asking for this to print an error on double frees.
Okay looks like I missed this instance though I do rember fixed another one.
I will fix it up.

> 
> > +/*
> > + * sst_get_sfreq - this function returns the frequency of the stream
> > + *
> > + * @str_param : stream params
> > + */
> > +int sst_get_num_channel(struct snd_sst_params *str_param)
> 
> Cut'n'paste error in the kerneldoc.
Oops will fix

-- 
~Vinod


[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2014-10-17 12:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 14:30 [PATCH v4 0/7] ASoC: Intel: sst - add the merrifield IPC driver Vinod Koul
2014-10-16 14:30 ` [PATCH v4 1/7] ASoC: Intel: mrfld - add the dsp sst driver Vinod Koul
2014-10-17  9:11   ` Mark Brown
2014-10-16 14:30 ` [PATCH v4 2/7] ASoC: Intel: mrfld - Add DSP load and management Vinod Koul
2014-10-17  9:44   ` Mark Brown
2014-10-17  9:18     ` Vinod Koul
2014-10-17 10:04       ` Takashi Iwai
2014-10-17 12:01         ` Mark Brown
2014-10-17 12:07           ` Takashi Iwai
2014-10-20  5:41             ` Vinod Koul
2014-10-20 15:29               ` Mark Brown
2014-10-20 16:07                 ` Vinod Koul
2014-10-16 14:30 ` [PATCH v4 3/7] ASoC: Intel: sst - add pcm ops handling Vinod Koul
2014-10-17 12:07   ` Mark Brown
2014-10-17 11:35     ` Vinod Koul [this message]
2014-10-16 14:30 ` [PATCH v4 4/7] ASoC: Intel: sst: Add IPC handling Vinod Koul
2014-10-17 12:09   ` Mark Brown
2014-10-17 11:55     ` Vinod Koul
2014-10-17 13:53       ` Mark Brown
2014-10-20  5:18         ` Vinod Koul
2014-10-16 14:30 ` [PATCH v4 5/7] ASoC: Intel: sst: add stream operations Vinod Koul
2014-10-16 14:30 ` [PATCH v4 6/7] ASoC: Intel: sst: Add some helper functions Vinod Koul
2014-10-16 14:30 ` [PATCH v4 7/7] ASoC: Intel: sst: Add makefile and kconfig changes Vinod Koul
2014-10-17 12:15 ` [PATCH v4 0/7] ASoC: Intel: sst - add the merrifield IPC driver Mark Brown
2014-10-17 11:56   ` Vinod Koul

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=20141017113523.GR1638@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=subhransu.s.prusty@intel.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