From: Dan Carpenter <dan.carpenter@oracle.com>
To: Jyri Sarha <jsarha@ti.com>
Cc: "Ujfalusi, Peter" <peter.ujfalusi@ti.com>,
alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>
Subject: Re: ASoC: davinci-mcasp: Set rule constraints if implicit BCLK divider is used
Date: Mon, 13 Apr 2015 15:16:40 +0300 [thread overview]
Message-ID: <20150413121639.GU16501@mwanda> (raw)
In-Reply-To: <552BAADA.5060401@ti.com>
Thanks for looking at this. I haven't double checked your analysis, but
512 means the stack is 2k and that's too high. I think there is
supposed to be a build warning if we use more than 1k of stack in a
function?
It's better to allocate it with kmalloc() and free it at the end.
regards,
dan carpenter
next prev parent reply other threads:[~2015-04-13 12:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 9:33 ASoC: davinci-mcasp: Set rule constraints if implicit BCLK divider is used Dan Carpenter
2015-04-13 11:39 ` Jyri Sarha
2015-04-13 12:16 ` Dan Carpenter [this message]
2015-04-13 13:32 ` Jyri Sarha
2015-04-13 13:58 ` Dan Carpenter
2015-04-13 14:22 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2015-03-27 6:20 Dan Carpenter
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=20150413121639.GU16501@mwanda \
--to=dan.carpenter@oracle.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jsarha@ti.com \
--cc=peter.ujfalusi@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