From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] Kernel crash on Allwinner H3 due to sound core changes
Date: Fri, 9 Mar 2018 11:14:19 +0000 [thread overview]
Message-ID: <20180309111419.GA5252@sirena.org.uk> (raw)
In-Reply-To: <87h8pq166i.wl%kuninori.morimoto.gx@renesas.com>
On Thu, Mar 08, 2018 at 11:49:18PM +0000, Kuninori Morimoto wrote:
> previous my patch used new flag (= .alloced_component),
> but I think it is not good idea.
> And I noticed that snd_soc_add_component() is
> also calling kfree(component) (= has same bug).
> So how about below one ?
> I want to post it instead of previous.
That should work also.
> # I will go to ELC next week, thus posting patch will be
> # 2weeks later
I'll be there as well.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180309/3f008113/attachment.sig>
prev parent reply other threads:[~2018-03-09 11:14 UTC|newest]
Thread overview: 10+ 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
[not found] ` <20180302124050.GF6255@sirena.org.uk>
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
[not found] ` <20180308111348.GB6019@sirena.org.uk>
2018-03-08 23:49 ` Kuninori Morimoto
2018-03-09 6:33 ` [alsa-devel] " Jernej Škrabec
2018-03-09 11:14 ` Mark Brown [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=20180309111419.GA5252@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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