Re: [PATCH] rpmsg: Release rpmsg devices in backends

2017-06-25 Thread Bjorn Andersson
On Fri 02 Jun 17:28 PDT 2017, Suman Anna wrote: > Hi Bjorn, > > On 06/02/2017 05:07 AM, Henri Roosen wrote: > > My suggestion would be to additionally change/fix > > rpmsg_register_device() so it will not overwrite the release callback. [..] > FWIW, I didn't run into any rpmsg device memory leaks

Re: [PATCH] rpmsg: Release rpmsg devices in backends

2017-06-02 Thread Suman Anna
Hi Bjorn, On 06/02/2017 05:07 AM, Henri Roosen wrote: >> The rpmsg devices are allocated in the backends and as such must be >> freed there as well. >> >> Signed-off-by: Bjorn Andersson >> --- >> drivers/rpmsg/qcom_smd.c | 11 +++ >> drivers/rpmsg/virtio_rpmsg_bus.c | 9

Re: [PATCH] rpmsg: Release rpmsg devices in backends

2017-06-02 Thread Henri Roosen
The rpmsg devices are allocated in the backends and as such must be freed there as well. Signed-off-by: Bjorn Andersson --- drivers/rpmsg/qcom_smd.c | 11 +++ drivers/rpmsg/virtio_rpmsg_bus.c | 9 + 2 files changed, 20 insertions(+) diff --git a/drivers/rpmsg/qcom_smd.

[PATCH] rpmsg: Release rpmsg devices in backends

2017-03-15 Thread Bjorn Andersson
The rpmsg devices are allocated in the backends and as such must be freed there as well. Signed-off-by: Bjorn Andersson --- drivers/rpmsg/qcom_smd.c | 11 +++ drivers/rpmsg/virtio_rpmsg_bus.c | 9 + 2 files changed, 20 insertions(+) diff --git a/drivers/rpmsg/qcom_smd.c