All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>,
	Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>
Cc: edubezval@gmail.com, daniel.lezcano@linaro.org,
	srinivas.pandruvada@linux.intel.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thermal: intel: int340x: processor_thermal_device: simplify to get driver data
Date: Mon, 22 Apr 2019 16:46:24 +0800	[thread overview]
Message-ID: <1555922784.26198.20.camel@intel.com> (raw)
In-Reply-To: <20190415162809.GU9224@smile.fi.intel.com>

On 一, 2019-04-15 at 19:28 +0300, Andy Shevchenko wrote:
> On Mon, Apr 15, 2019 at 08:18:30PM +0530, Sumeet Pawnikar wrote:
> > 
> > From: "Pawnikar, Sumeet R" <sumeet.r.pawnikar@intel.com>
> > 
> > This simplifies getting the 'driver_data' from 'struct device'
> > directly.
> > Going through platform_device or pci_dev is not required. Also
> > removes
> > condition check as the private data stored with dev pointer, means
> > irrespective of enumeration mode, we can use dev_get_drvdata().
> > This removes the unnecessary step back and forth.
> > 
> Indeed, good clean up!
> Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> 
Thanks, patch applied.

-rui
> > 
> > Signed-off-by: Sumeet Pawnikar <sumeet.r.pawnikar@intel.com>
> > ---
> >  .../int340x_thermal/processor_thermal_device.c     |   11 +-------
> > ---
> >  1 file changed, 1 insertion(+), 10 deletions(-)
> > 
> > diff --git
> > a/drivers/thermal/intel/int340x_thermal/processor_thermal_device.c
> > b/drivers/thermal/intel/int340x_thermal/processor_thermal_device.c
> > index 8e1cf4d..2a7cbaa 100644
> > ---
> > a/drivers/thermal/intel/int340x_thermal/processor_thermal_device.c
> > +++
> > b/drivers/thermal/intel/int340x_thermal/processor_thermal_device.c
> > @@ -81,22 +81,13 @@ enum proc_thermal_emum_mode_type {
> >  					struct device_attribute
> > *attr, \
> >  					char *buf) \
> >  { \
> > -	struct pci_dev *pci_dev; \
> > -	struct platform_device *pdev; \
> > -	struct proc_thermal_device *proc_dev; \
> > +	struct proc_thermal_device *proc_dev =
> > dev_get_drvdata(dev); \
> >  	\
> >  	if (proc_thermal_emum_mode == PROC_THERMAL_NONE) { \
> >  		dev_warn(dev, "Attempted to get power limit before
> > device was initialized!\n"); \
> >  		return 0; \
> >  	} \
> >  	\
> > -	if (proc_thermal_emum_mode == PROC_THERMAL_PLATFORM_DEV) {
> > \
> > -		pdev = to_platform_device(dev); \
> > -		proc_dev = platform_get_drvdata(pdev); \
> > -	} else { \
> > -		pci_dev = to_pci_dev(dev); \
> > -		proc_dev = pci_get_drvdata(pci_dev); \
> > -	} \
> >  	return sprintf(buf, "%lu\n",\
> >  	(unsigned long)proc_dev->power_limits[index].suffix *
> > 1000); \
> >  }
> > -- 
> > 1.7.9.5
> > 

  reply	other threads:[~2019-04-22  8:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 14:48 [PATCH] thermal: intel: int340x: processor_thermal_device: simplify to get driver data Sumeet Pawnikar
2019-04-15 16:28 ` Andy Shevchenko
2019-04-22  8:46   ` Zhang Rui [this message]
2019-04-22  8:55     ` Zhang Rui
2019-04-24 11:19       ` Pawnikar, Sumeet R

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=1555922784.26198.20.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=edubezval@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=sumeet.r.pawnikar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.