From: Linus Walleij <linus.walleij@linaro.org>
To: Jingoo Han <jg1.han@samsung.com>, Stephen Warren <swarren@wwwdotorg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: core: use devres_release() instead of devres_destroy()
Date: Fri, 1 Mar 2013 01:54:21 +0100 [thread overview]
Message-ID: <CACRpkdZBbuxogFy7NXiPnf4FR_eO2KJVck4C80dZZXuAZTsQzQ@mail.gmail.com> (raw)
In-Reply-To: <009401ce13c9$c01f6400$405e2c00$%han@samsung.com>
On Tue, Feb 26, 2013 at 3:34 AM, Jingoo Han <jg1.han@samsung.com> wrote:
> devres_release() can simplify the code, because devres_release()
> will call the destructor for the resource as well as freeing
> the devres data.
>
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
Hm, Stephen, you OK with this?
Yours,
Linus Walleij
next prev parent reply other threads:[~2013-03-01 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 2:34 [PATCH] pinctrl: core: use devres_release() instead of devres_destroy() Jingoo Han
2013-03-01 0:54 ` Linus Walleij [this message]
2013-03-01 1:11 ` Stephen Warren
2013-03-01 12:30 ` Linus Walleij
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=CACRpkdZBbuxogFy7NXiPnf4FR_eO2KJVck4C80dZZXuAZTsQzQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).