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>
Subject: Re: [PATCHv4 1/9] extcon: Add extcon_dev_allocate/free() to control the memory of extcon device
Date: Fri, 25 Apr 2014 10:12:22 -0500 [thread overview]
Message-ID: <20140425151222.GE29632@saruman.home> (raw)
In-Reply-To: <1398386544-16295-2-git-send-email-cw00.choi@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
On Fri, Apr 25, 2014 at 09:42:16AM +0900, Chanwoo Choi wrote:
> This patch add APIs to control the extcon device on extcon provider driver.
> The extcon_dev_allocate() allocates the memory of extcon device and initializes
> supported cables. And then extcon_dev_free() decrement the reference of the
> device of extcon device and free the memory of the extcon device. This APIs
> must need to implement devm_extcon_dev_allocate()/free() APIs.
>
> Signed-off-by: Chanwoo Choi <cw00.choi@samsung.com>
except for the one comment below, you can add:
Reviewed-by: Felipe Balbi <balbi@ti.com>
> @@ -267,6 +273,13 @@ static inline int devm_extcon_dev_register(struct device *dev,
> static inline void devm_extcon_dev_unregister(struct device *dev,
> struct extcon_dev *edev) { }
>
> +static inline struct extcon_dev *extcon_dev_allocate(const char **cables)
> +{
> + return ERR_PTR(-ENOMEM);
so this is executed when extcon isn't enabled right ? -ENOMEM is kind of
lying to your user. You're telling the user that you don't have memory
when in reality you didn't implement this function. -ENOSYS looks like a
better choice
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-04-25 15:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 0:42 [PATCHv4 0/9] extcon: Support devm_extcon_dev_allocate/free() Chanwoo Choi
2014-04-25 0:42 ` [PATCHv4 1/9] extcon: Add extcon_dev_allocate/free() to control the memory of extcon device Chanwoo Choi
2014-04-25 15:12 ` Felipe Balbi [this message]
2014-04-25 0:42 ` [PATCHv4 2/9] extcon: Add devm_extcon_dev_allocate/free to manage the resource " Chanwoo Choi
2014-04-25 15:14 ` Felipe Balbi
2014-04-25 0:42 ` [PATCHv4 3/9] extcon: max8997: Use devm_extcon_dev_allocate for extcon_dev Chanwoo Choi
2014-04-25 15:14 ` Felipe Balbi
2014-04-25 0:42 ` [PATCHv4 4/9] extcon: max77693: " Chanwoo Choi
2014-04-25 15:15 ` Felipe Balbi
2014-04-25 0:42 ` [PATCHv4 5/9] extcon: max14577: " Chanwoo Choi
2014-04-25 15:16 ` Felipe Balbi
2014-04-25 0:42 ` [PATCHv4 6/9] extcon: arizona: " Chanwoo Choi
2014-04-25 15:16 ` Felipe Balbi
2014-04-25 0:42 ` [PATCHv4 7/9] extcon: adc-jack: " Chanwoo Choi
2014-04-25 15:17 ` Felipe Balbi
2014-04-25 0:42 ` [PATCHv4 8/9] extcon: gpio: " Chanwoo Choi
2014-04-25 15:18 ` Felipe Balbi
2014-04-25 0:42 ` [PATCHv4 9/9] extcon: palmas: " Chanwoo Choi
2014-04-28 10:24 ` Lee Jones
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=20140425151222.GE29632@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=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.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
Powered by JetHome