linux-kernel - Re: [alsa-devel] [PATCH v1 3/3] ASoC: soc-core: fix platform name vs. of

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8736q1b2w8.wl-kuninori.morimoto.gx@renesas.com>
Date:   10 Jan 2019 12:46:29 +0900
From:   Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
To:     Mark Brown <broonie@...nel.org>, Jon Hunter <jonathanh@...dia.com>
Cc:     Liam Girdwood <lgirdwood@...il.com>, linux-tegra@...r.kernel.org,
        Matthias Reichl <hias@...us.com>, alsa-devel@...a-project.org,
        Marcel Ziswiler <marcel.ziswiler@...adex.com>,
        Takashi Iwai <tiwai@...e.com>, linux-kernel@...r.kernel.org,
        Marcel Ziswiler <marcel@...wiler.com>
Subject: Re: [alsa-devel] [PATCH v1 3/3] ASoC: soc-core: fix platform name vs. of_node assignement


Hi Mark, Jon again

> My posted quick-patch can solve "dirty pointer" issue,
> but it can't solve "memory leak" issue.
> This issue will be solved if all driver can switch to
> modern style, but it needs more time.
> Are these correct ?

Sorry I was very confused.
I think the issue is only "dirty pointer",
there is no "memory leak" issue (= devm_kzalloc()).

And the things Jon is worry about is that why we need to
have platform pointer.
And the answer is we need multi platform support in the future
(pointer is prepare for it).
Are these correct ?

If so my posted patch can solve all issues ?

Best regards
---
Kuninori Morimoto