From: Kevin Hilman <khilman@deeprootsystems.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: davinci-linux-open-source@linux.davincidsp.com,
alsa-devel@alsa-project.org,
Troy Kisky <troy.kisky@boundarydevices.com>
Subject: Re: [PATCH] RFC: ASoC: Davinci: Fix data_type divide by zero
Date: Mon, 14 Sep 2009 15:04:16 -0700 [thread overview]
Message-ID: <87ws41uqsf.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20090912121917.GA4633@sirena.org.uk> (Mark Brown's message of "Sat\, 12 Sep 2009 13\:19\:17 +0100")
Mark Brown <broonie@opensource.wolfsonmicro.com> writes:
> On Fri, Sep 11, 2009 at 02:27:18PM -0700, Troy Kisky wrote:
>> Mark Brown wrote:
>
>> >> + * dma_params must be first because rtd->dai->cpu_dai->private_data
>> >> + * is cast to an array of struct davinci_pcm_dma_params ** in
>> >> + * davinci_pcm_open.
>> >> + */
>
>> > Is it not possible to deal with this by going through the types
>> > properly? The comment sets off all sorts of alarm bells.
>
>> private_data will be either struct davinci_mcbsp_dev or
>> struct davinci_audio_dev
>
> Hrm. Might be nice to change that :/
>
>> Btw, I'm about to submit another rev of this against your for32
>> branch. But your branch currently give compile errors, so it
>> my compile test just doesn't generate new errors.
>
> You'll need to merge it with Kevin's branch to build - or wait for -rc1
> when everything should've made it into mainline. Kevin's git has a
> branch temp/asoc with the merge done in it.
Also, I just pushed a new temp/asoc which is a simple merge of current
davinci git master and Mark's for-2.6.32 branch.
Kevin
prev parent reply other threads:[~2009-09-14 22:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 1:57 [PATCH] RFC: ASoC: Davinci: Fix data_type divide by zero Troy Kisky
2009-09-11 10:31 ` Mark Brown
2009-09-11 21:27 ` Troy Kisky
2009-09-12 12:19 ` Mark Brown
2009-09-14 22:04 ` Kevin Hilman [this message]
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=87ws41uqsf.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=troy.kisky@boundarydevices.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