Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: gsantosh@codeaurora.org
Cc: Vinod Koul <vinod.koul@intel.com>,
	alsa-devel@alsa-project.org,
	"Clemens Ladisch   lgirdwood@gmail.com" <lgirdwood@gmail.com>
Subject: Re: Question on compress offload framework memory corruption
Date: Thu, 19 Dec 2013 10:55:08 +0000	[thread overview]
Message-ID: <20131219105508.GV31886@sirena.org.uk> (raw)
In-Reply-To: <63ac7c9c1f4ac8d8ef0ed9587fd1cf5f.squirrel@www.codeaurora.org>


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

On Wed, Dec 18, 2013 at 01:17:51PM -0000, gsantosh@codeaurora.org wrote:
> Hi,
> 
> I have following questions in the compressed offload framework API.
> 
> static int soc_compr_set_params_fe(struct snd_compr_stream *cstream,
> 					struct snd_compr_params *params)
> {
> ...
> 	hw_params = kzalloc(sizeof(*hw_params), GFP_KERNEL);
> 	if (hw_params == NULL)
> 		return -ENOMEM;
> /*1st question is, what is the use of above allocated memory I do not see
> this being used in this function*/

The code you're quoting there isn't in mainline.  I've also added Vinod
to the CCs, you probably want to include him in any discussion of the
compressed API.

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

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



  parent reply	other threads:[~2013-12-19 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-18 13:17 Question on compress offload framework memory corruption gsantosh
2013-12-19  7:59 ` gsantosh
2013-12-19 10:42 ` Clemens Ladisch
2013-12-19 10:55 ` Mark Brown [this message]
2014-01-05 14:04   ` Vinod Koul
  -- strict thread matches above, loose matches on Subject: below --
2014-03-04 22:19 Banajit Goswami
2014-03-05  7:51 ` 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=20131219105508.GV31886@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=gsantosh@codeaurora.org \
    --cc=lgirdwood@gmail.com \
    --cc=vinod.koul@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