public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Darius Augulis <augulis.darius-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org,
	Sascha Hauer <s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>,
	Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V2 1/9] New drivers for MXC: add I2C support for MXC
Date: Wed, 25 Mar 2009 13:06:29 +0200	[thread overview]
Message-ID: <49CA1035.4000906@gmail.com> (raw)
In-Reply-To: <20090325105931.GC3029-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

Wolfram Sang wrote:
> Hi Darius,
>
> this is not V5, is it? See below...Was there much rebasing needed for 2.6.29? Otherwise we could simply
> keep this one?
>
> http://article.gmane.org/gmane.linux.drivers.i2c/2962
>
>   
Please keep and merge new patch.

>> +
>> +	pdata = pdev->dev.platform_data;
>> +	if (!pdata) {
>> +		dev_err(&pdev->dev, "I2C driver needs platform data\n");
>> +		return -ENODEV;
>> +	}
>> +
>> +	if (pdata->init) {
>> +		ret = pdata->init(&pdev->dev);
>> +		if (ret)
>> +			return ret;
>> +	}
>> +
>>     
>
> For example, V5 stuff looked like this:
>
> 	pdata = pdev->dev.platform_data;
>
> 	if (pdata && pdata->init) {
> 		ret = pdata->init(&pdev->dev);
> 		if (ret)
> 			return ret;
> 	}
>
> which is better.

New one is better. Because one could not have anything to init in the board.

      parent reply	other threads:[~2009-03-25 11:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25  9:02 [PATCH V2 1/9] New drivers for MXC: add I2C support for MXC Darius Augulis
     [not found] ` <49C9F337.4080102-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-03-25  9:29   ` Darius Augulis
2009-03-25 10:59   ` Wolfram Sang
     [not found]     ` <20090325105931.GC3029-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-03-25 11:06       ` Darius Augulis [this message]

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=49CA1035.4000906@gmail.com \
    --to=augulis.darius-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=linux-arm-kernel-xIg/pKzrS19vn6HldHNs0ANdhmdF6hFW@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=s.hauer-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    --cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@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