From: julia.lawall@lip6.fr (Julia Lawall)
To: linux-arm-kernel@lists.infradead.org
Subject: question about drivers/pinctrl/pinctrl-at91.c
Date: Tue, 11 Dec 2012 10:59:27 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1212111059090.2091@hadrien> (raw)
In-Reply-To: <CACRpkdb-yzpg2SJ--ksjM8TDu1cuCxMCn1cHj9OPQQt7DsjHeQ@mail.gmail.com>
On Tue, 11 Dec 2012, Linus Walleij wrote:
> On Tue, Dec 11, 2012 at 10:04 AM, Julia Lawall <julia.lawall@lip6.fr> wrote:
> > On Tue, 11 Dec 2012, Linus Walleij wrote:
>
> >> I was under the impression that if you exit the probe function
> >> with a negative value anything allocated with devm_* was freed
> >> immediately, that is atleast how it's described in
> >> Documentation/driver-model/devres.txt
> >> atleast that seems to be the intetion with the whole thing.
> >
> > That is true, but I wasn't sure taht this function was part of the probe
> > function. Its only reference is in:
> >
> > static struct pinctrl_ops at91_pctrl_ops = {
> > .get_groups_count = at91_get_groups_count,
> > .get_group_name = at91_get_group_name,
> > .get_group_pins = at91_get_group_pins,
> > .pin_dbg_show = at91_pin_dbg_show,
> > .dt_node_to_map = at91_dt_node_to_map,
> > .dt_free_map = at91_dt_free_map,
> > };
> >
> > Working backwards, one possible call site is pinctrl_get, which is an
> > exported function. Is it safe to assume that it will always be called
> > from within a probe function?
>
> Aha sorry I got it all backwards :-(
>
> Well, yes in that case it's devm_kfree() for sure.
I've sent a patch, thanks.
julia
next prev parent reply other threads:[~2012-12-11 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 15:52 question about drivers/pinctrl/pinctrl-at91.c Julia Lawall
2012-12-11 8:51 ` Linus Walleij
2012-12-11 9:04 ` Julia Lawall
2012-12-11 9:08 ` Linus Walleij
2012-12-11 9:59 ` Julia Lawall [this message]
2012-12-11 9:06 ` Grant Likely
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=alpine.DEB.2.02.1212111059090.2091@hadrien \
--to=julia.lawall@lip6.fr \
--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