linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: <linux-kernel@vger.kernel.org>, <myungjoo.ham@samsung.com>,
	<balbi@ti.com>, <gg@slimlogic.co.uk>, <kishon@ti.com>,
	<ckeepax@opensource.wolfsonmicro.com>, <broonie@kernel.org>,
	<k.kozlowski@samsung.com>, <kyungmin.park@samsung.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCHv2 6/9] extcon: palmas: Use devm_extcon_dev_allocate for extcon_dev
Date: Thu, 24 Apr 2014 09:10:29 -0500	[thread overview]
Message-ID: <20140424141029.GA26661@saruman.home> (raw)
In-Reply-To: <1398081742-24277-7-git-send-email-cw00.choi@samsung.com>

[-- Attachment #1: Type: text/plain, Size: 657 bytes --]

On Mon, Apr 21, 2014 at 09:02:19PM +0900, Chanwoo Choi wrote:
> This patch use devm_extcon_dev_allocate() to simplify the memory control
> of extcon device.
> 
> Cc: Graeme Gregory <gg@slimlogic.co.uk>
> Cc: Kishon Vijay Abraham I <kishon@ti.com>
> Cc: Felipe Balbi <balbi@ti.com>
> Cc: Samuel Ortiz <sameo@linux.intel.com>
> Cc: Lee Jones <lee.jones@linaro.org>
> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>

Tested on OMAP5 uEVM, please remember to fix up ordering in your
extcon-next branch to avoid introducing a non-bisectable history.

Tested-by: Felipe Balbi <balbi@ti.com>
Acked-by: Felipe Balbi <balbi@ti.com>

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2014-04-24 14:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-21 12:02 [PATCHv2 0/9] extcon: Support devm_extcon_dev_allocate/free() Chanwoo Choi
2014-04-21 12:02 ` [PATCHv2 1/9] extcon: Add extcon_dev_allocate/free() to control the memory of extcon device Chanwoo Choi
2014-04-21 12:02 ` [PATCHv2 2/9] extcon: Add devm_extcon_dev_allocate/free to manage the resource " Chanwoo Choi
2014-04-21 12:02 ` [PATCHv2 3/9] extcon: max8997: Use devm_extcon_dev_allocate for extcon_dev Chanwoo Choi
2014-04-22  8:17   ` Krzysztof Kozlowski
2014-04-21 12:02 ` [PATCHv2 4/9] extcon: max77693: " Chanwoo Choi
2014-04-22  8:18   ` Krzysztof Kozlowski
2014-04-21 12:02 ` [PATCHv2 5/9] extcon: max14577: " Chanwoo Choi
2014-04-22  8:18   ` Krzysztof Kozlowski
2014-04-21 12:02 ` [PATCHv2 6/9] extcon: palmas: " Chanwoo Choi
2014-04-23 13:38   ` Lee Jones
2014-04-23 13:55     ` Lee Jones
2014-04-24  5:22   ` Chanwoo Choi
2014-04-24 14:10   ` Felipe Balbi [this message]
2014-04-21 12:02 ` [PATCHv2 7/9] extcon: arizona: " Chanwoo Choi
2014-04-21 12:55   ` Charles Keepax
2014-04-21 12:02 ` [PATCHv2 8/9] extcon: adc-jack: " Chanwoo Choi
2014-04-21 12:02 ` [PATCHv2 9/9] extcon: gpio: " Chanwoo Choi

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=20140424141029.GA26661@saruman.home \
    --to=balbi@ti.com \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=cw00.choi@samsung.com \
    --cc=gg@slimlogic.co.uk \
    --cc=k.kozlowski@samsung.com \
    --cc=kishon@ti.com \
    --cc=kyungmin.park@samsung.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=sameo@linux.intel.com \
    /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).