From: Eduardo Valentin <edubezval@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
LKML <linux-kernel@vger.kernel.org>,
Kukjin Kim <kgene@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-samsung-soc <linux-samsung-soc@vger.kernel.org>
Subject: Re: [PATCHv2 1/1] cpufreq: exynos: allow modular build
Date: Mon, 2 Feb 2015 14:22:15 -0400 [thread overview]
Message-ID: <20150202182213.GF17425@developer.hsd1.ca.comcast.net> (raw)
In-Reply-To: <CAKohpondsvLm2S_V+aBSoCg252nHONJ6TbyTuHoVYuwxBDEuDA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
On Mon, Feb 02, 2015 at 09:33:09AM +0530, Viresh Kumar wrote:
> On 1 February 2015 at 00:29, Eduardo Valentin <edubezval@gmail.com> wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> >
<big cut>
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Thanks!
>
> Now as these are all compilable as modules, should we look into the drivers as
> well to see what they are doing on module unload ?
hmm.. it seams to be the case, yes. From a quick look, there are unreleased resources
that needs to be freed. However, they are not really on module unload,
but on device removal. Which should be a reproducible but even today, in
case one manually unbinds the device.
Let me have a look here and will be sending something soon.
Thanks,
Eduardo Valentin
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: edubezval@gmail.com (Eduardo Valentin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 1/1] cpufreq: exynos: allow modular build
Date: Mon, 2 Feb 2015 14:22:15 -0400 [thread overview]
Message-ID: <20150202182213.GF17425@developer.hsd1.ca.comcast.net> (raw)
In-Reply-To: <CAKohpondsvLm2S_V+aBSoCg252nHONJ6TbyTuHoVYuwxBDEuDA@mail.gmail.com>
On Mon, Feb 02, 2015 at 09:33:09AM +0530, Viresh Kumar wrote:
> On 1 February 2015 at 00:29, Eduardo Valentin <edubezval@gmail.com> wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> >
<big cut>
>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
Thanks!
>
> Now as these are all compilable as modules, should we look into the drivers as
> well to see what they are doing on module unload ?
hmm.. it seams to be the case, yes. From a quick look, there are unreleased resources
that needs to be freed. However, they are not really on module unload,
but on device removal. Which should be a reproducible but even today, in
case one manually unbinds the device.
Let me have a look here and will be sending something soon.
Thanks,
Eduardo Valentin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150202/b3f7e5ad/attachment.sig>
next prev parent reply other threads:[~2015-02-02 18:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 18:59 [PATCHv2 1/1] cpufreq: exynos: allow modular build Eduardo Valentin
2015-01-31 18:59 ` Eduardo Valentin
2015-02-02 4:03 ` Viresh Kumar
2015-02-02 4:03 ` Viresh Kumar
2015-02-02 4:03 ` Viresh Kumar
2015-02-02 18:22 ` Eduardo Valentin [this message]
2015-02-02 18:22 ` Eduardo Valentin
2015-02-02 18:22 ` Eduardo Valentin
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=20150202182213.GF17425@developer.hsd1.ca.comcast.net \
--to=edubezval@gmail.com \
--cc=arnd@arndb.de \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.