From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: linux-input@vger.kernel.org, patches@linaro.org,
Kukjin Kim <kgene.kim@samsung.com>
Subject: Re: [PATCH v2] Input: samsung-keypad - Use devm_* functions
Date: Tue, 27 Nov 2012 02:13:21 -0800 [thread overview]
Message-ID: <20121127101320.GD25658@core.coreip.homeip.net> (raw)
In-Reply-To: <1354010091-31294-1-git-send-email-sachin.kamat@linaro.org>
On Tue, Nov 27, 2012 at 03:24:51PM +0530, Sachin Kamat wrote:
> devm_* functions are device managed and make error handling
> and code simpler. While at it also fix error exit paths.
>
Is this different from the version I sent you?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2012-11-27 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 9:54 [PATCH v2] Input: samsung-keypad - Use devm_* functions Sachin Kamat
2012-11-27 10:13 ` Dmitry Torokhov [this message]
2012-11-27 10:14 ` Dmitry Torokhov
2012-11-27 10:24 ` Sachin Kamat
2012-11-28 5:57 ` Sachin Kamat
2012-11-28 6:30 ` Dmitry Torokhov
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=20121127101320.GD25658@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=linux-input@vger.kernel.org \
--cc=patches@linaro.org \
--cc=sachin.kamat@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 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).