All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Bhumika Goyal <bhumirks@gmail.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
	Eduardo Valentin <edubezval@gmail.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jacob Pan <jacob.jun.pan@linux.intel.com>
Subject: Re: [PATCH] thermal/intel_powerclamp: add const to thermal_cooling_device_ops structure
Date: Thu, 29 Jun 2017 20:08:33 +0800	[thread overview]
Message-ID: <1498738113.2510.40.camel@intel.com> (raw)
In-Reply-To: <CAOH+1jHKLf+PVY=g4iXZcT5mKbskuVki5Lcwb1w=AgnVRtksYg@mail.gmail.com>

On Thu, 2017-06-29 at 11:26 +0530, Bhumika Goyal wrote:
> On Thu, Jun 29, 2017 at 11:02 AM, Zhang Rui <rui.zhang@intel.com>
> wrote:
> > 
> > On Thu, 2017-06-29 at 10:41 +0530, Bhumika Goyal wrote:
> > > 
> > > On Thu, Jun 29, 2017 at 8:30 AM, Zhang Rui <rui.zhang@intel.com>
> > > wrote:
> > > > 
> > > > 
> > > > On Wed, 2017-06-21 at 12:39 +0530, Bhumika Goyal wrote:
> > > > > 
> > > > > 
> > > > > Declare thermal_cooling_device_ops structure as const as it
> > > > > is
> > > > > only
> > > > > passed
> > > > > as an argument to the function
> > > > > thermal_cooling_device_register
> > > > > and
> > > > > this
> > > > > argument is of type const. So, declare the structure as
> > > > > const.
> > > > > 
> > > > I checked the source and the code is written in this way as
> > > > well in
> > > > some other drivers, why not fix them altogether?
> > > > 
> > > Hey,
> > > 
> > > I have already sent the patches for the drivers requiring this
> > > change.
> > > Some of them got applied as well.
> > I mean the other drivers that use thermal_cooling_device_ops.
> > 
> Actually, I also meant the same but maybe I wasn't clear enough :)
> 
> > 
> > Surely I can applied this patch, but still it would be nice if you
> > can
> > check the other places that defines thermal_cooling_device_ops and
> > fix
> > all of them in one time. :)
> > 
> I checked again and there remains only one file in power/supply where
> thermal_cooling_device_ops can be made const. I will submit a patch
> for it but I think I will have to create a separate patch because the
> maintainers are different.
> All other places are either already const


>  or I have submitted patches
> for them

am I in the loop of the patches? because I was not aware of those
changes.

thanks,
rui
>  or cannot be made const.
> 
> Thanks,
> Bhumika
> 
> > 
> > thanks,
> > rui
> > > 
> > > 
> > > Thanks,
> > > Bhumika
> > > 
> > > > 
> > > > 
> > > > thanks,
> > > > rui
> > > > > 
> > > > > 
> > > > > Signed-off-by: Bhumika Goyal <bhumirks@gmail.com>
> > > > > ---
> > > > >  drivers/thermal/intel_powerclamp.c | 2 +-
> > > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > > 
> > > > > diff --git a/drivers/thermal/intel_powerclamp.c
> > > > > b/drivers/thermal/intel_powerclamp.c
> > > > > index d718cd1..e4c68b7 100644
> > > > > --- a/drivers/thermal/intel_powerclamp.c
> > > > > +++ b/drivers/thermal/intel_powerclamp.c
> > > > > @@ -659,7 +659,7 @@ static int
> > > > > powerclamp_set_cur_state(struct
> > > > > thermal_cooling_device *cdev,
> > > > >  }
> > > > > 
> > > > >  /* bind to generic thermal layer as cooling device*/
> > > > > -static struct thermal_cooling_device_ops
> > > > > powerclamp_cooling_ops
> > > > > = {
> > > > > +static const struct thermal_cooling_device_ops
> > > > > powerclamp_cooling_ops = {
> > > > >       .get_max_state = powerclamp_get_max_state,
> > > > >       .get_cur_state = powerclamp_get_cur_state,
> > > > >       .set_cur_state = powerclamp_set_cur_state,

      reply	other threads:[~2017-06-29 12:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21  7:09 [PATCH] thermal/intel_powerclamp: add const to thermal_cooling_device_ops structure Bhumika Goyal
2017-06-29  3:00 ` Zhang Rui
2017-06-29  5:11   ` Bhumika Goyal
2017-06-29  5:32     ` Zhang Rui
2017-06-29  5:56       ` Bhumika Goyal
2017-06-29 12:08         ` Zhang Rui [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=1498738113.2510.40.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=bhumirks@gmail.com \
    --cc=edubezval@gmail.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=julia.lawall@lip6.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.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 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.