From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: "Jernej Škrabec" <jernej.skrabec@siol.net>,
maxime.ripard@free-electrons.com, wens@csie.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [BUG] Kernel crash on Allwinner H3 due to sound core changes
Date: Thu, 8 Mar 2018 11:13:48 +0000 [thread overview]
Message-ID: <20180308111348.GB6019@sirena.org.uk> (raw)
In-Reply-To: <87efkvtldx.wl%kuninori.morimoto.gx@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
On Thu, Mar 08, 2018 at 01:21:02AM +0000, Kuninori Morimoto wrote:
> Ahh.. indeed. Good catch !
> How about to add such flag ?
> This is just idea. No tested, No compiled, but can help you ?
I think this makes sense as a patch. We might want to disallow
allocating components as part of a bigger struct so everything is more
consistent but that's a bigger thing.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-03-08 11:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 21:02 [BUG] Kernel crash on Allwinner H3 due to sound core changes Jernej Škrabec
2018-03-01 1:49 ` Kuninori Morimoto
2018-03-01 22:23 ` Jernej Škrabec
2018-03-02 12:40 ` Mark Brown
2018-03-05 21:30 ` Jernej Škrabec
2018-03-07 21:11 ` Jernej Škrabec
2018-03-08 1:21 ` Kuninori Morimoto
2018-03-08 6:03 ` [alsa-devel] " Jernej Škrabec
2018-03-08 11:13 ` Mark Brown [this message]
2018-03-08 23:49 ` Kuninori Morimoto
2018-03-09 6:33 ` [alsa-devel] " Jernej Škrabec
2018-03-09 11:14 ` Mark Brown
2018-03-19 8:08 ` Applied "soc-core: don't call kfree() for component" to the asoc tree Mark Brown
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=20180308111348.GB6019@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jernej.skrabec@siol.net \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=wens@csie.org \
/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