mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Nizam Haider <nizamhaider786@gmail.com>,
	knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
	gregkh@linuxfoundation.org, hamohammed.sa@gmail.com,
	shivanib134@gmail.com, asaf.vertz@tandemg.com,
	cristina.moraru09@gmail.com
Cc: linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, Nizam Haider <nijamh@cdac.in>
Subject: Re: [PATCH] Staging: iio: light: tsl2x7x_core: use dev_get_platdata()
Date: Sun, 29 Nov 2015 15:22:01 +0000	[thread overview]
Message-ID: <565B1819.9030807@kernel.org> (raw)
In-Reply-To: <1448300930-10789-1-git-send-email-nizamhaider786@gmail.com>

On 23/11/15 17:48, Nizam Haider wrote:
> Use the wrapper function for retrieving the platform data instead of
> accessing dev->platform_data directly.
> 
> Signed-off-by: Nizam Haider <nijamh@cdac.in>
Applied to the togreg branch of iio.git - initially pushed out as testing.
Note that branch will get rebased shortly to catch up with Greg's staging-next.

Thanks,

Jonathan
> ---
>  drivers/staging/iio/light/tsl2x7x_core.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/iio/light/tsl2x7x_core.c b/drivers/staging/iio/light/tsl2x7x_core.c
> index 9dfd048..5b1c165 100644
> --- a/drivers/staging/iio/light/tsl2x7x_core.c
> +++ b/drivers/staging/iio/light/tsl2x7x_core.c
> @@ -1898,7 +1898,7 @@ static int tsl2x7x_probe(struct i2c_client *clientp,
>  	mutex_init(&chip->prox_mutex);
>  
>  	chip->tsl2x7x_chip_status = TSL2X7X_CHIP_UNKNOWN;
> -	chip->pdata = clientp->dev.platform_data;
> +	chip->pdata = dev_get_platdata(&clientp->dev);
>  	chip->id = id->driver_data;
>  	chip->chip_info =
>  		&tsl2x7x_chip_info_tbl[device_channel_config[id->driver_data]];
> 


      reply	other threads:[~2015-11-29 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 17:48 Nizam Haider
2015-11-29 15:22 ` Jonathan Cameron [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=565B1819.9030807@kernel.org \
    --to=jic23@kernel.org \
    --cc=asaf.vertz@tandemg.com \
    --cc=cristina.moraru09@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hamohammed.sa@gmail.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nijamh@cdac.in \
    --cc=nizamhaider786@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=shivanib134@gmail.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