devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Andreas Dannenberg <dannenberg-l0cyMroinI0@public.gmane.org>,
	linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH v3 1/2] iio: light: add support for TI's opt3001 light sensor
Date: Sun, 19 Jul 2015 14:16:17 +0100	[thread overview]
Message-ID: <55ABA321.1030800@kernel.org> (raw)
In-Reply-To: <559D5366.8030003-l0cyMroinI0@public.gmane.org>

On 08/07/15 17:44, Andreas Dannenberg wrote:
> On 07/05/2015 09:08 AM, Jonathan Cameron wrote:
> <snip>
>> Looking pretty good to me, though I'd like to give Peter time to take
>> another look and give his reviewed-by etc.
>>
>> One really minor suggestion from me...
>> <snip>
>>> +
>>> +static int opt3001_probe(struct i2c_client *client,
>>> +		const struct i2c_device_id *id)
>>> +{
>>> +	struct device *dev = &client->dev;
>>> +
>>> +	struct iio_dev *iio;
>>> +	struct opt3001 *opt;
>>> +	int irq = client->irq;
>>> +	int ret = -ENOMEM;
>>> +
>>> +	iio = devm_iio_device_alloc(dev, sizeof(*opt));
>>> +	if (!iio)
>> return -ENOMEM; would be cleaner, then there is no need to initialize
>> ret either.
> 
> Hi Jonathan,
> thanks for looking at my code. While we are waiting for additional feedback would you
> like me to go ahead and re-spin/re-test the patch with your latest suggestion?
> 
> Regards,
> 
Not to worry, I made that trivial change when applying.
There was also some fuzz in the makefiles and kconfig as
a result of other drivers going in, but all trivial.

Applied to the togreg branch of iio.git.

Thanks,

Jonathan

  parent reply	other threads:[~2015-07-19 13:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 22:27 [PATCH v3 0/2] iio: light: add support for TI's opt3001 light sensor Andreas Dannenberg
     [not found] ` <1435876079-26287-1-git-send-email-dannenberg-l0cyMroinI0@public.gmane.org>
2015-07-02 22:27   ` [PATCH v3 1/2] " Andreas Dannenberg
     [not found]     ` <1435876079-26287-2-git-send-email-dannenberg-l0cyMroinI0@public.gmane.org>
2015-07-05 14:08       ` Jonathan Cameron
     [not found]         ` <55993A4C.10105-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-07-08 16:44           ` Andreas Dannenberg
     [not found]             ` <559D5366.8030003-l0cyMroinI0@public.gmane.org>
2015-07-19 13:16               ` Jonathan Cameron [this message]
2015-07-02 22:27   ` [PATCH v3 2/2] iio: light: opt3001: Add device tree binding documentation Andreas Dannenberg
     [not found]     ` <1435876079-26287-3-git-send-email-dannenberg-l0cyMroinI0@public.gmane.org>
2015-07-05 14:09       ` Jonathan Cameron
     [not found]         ` <55993A7D.7090806-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-07-19 13:17           ` Jonathan Cameron
     [not found]             ` <55ABA358.3040700-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-07-20 18:22               ` Andreas Dannenberg
     [not found]                 ` <55AD3C72.4050607-l0cyMroinI0@public.gmane.org>
2015-07-23 20:02                   ` Jonathan Cameron

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=55ABA321.1030800@kernel.org \
    --to=jic23-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=balbi-l0cyMroinI0@public.gmane.org \
    --cc=dannenberg-l0cyMroinI0@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).