public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Colin Leroy <colin@colino.net>
Cc: Roel Kluin <12o3l@tiscali.nl>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: ADT746X: logical-bitwise & confusion in set_max_duty_at_crit()
Date: Mon, 10 Mar 2008 19:06:53 +1100	[thread overview]
Message-ID: <1205136413.8621.3.camel@pasglop> (raw)
In-Reply-To: <20080310084633.5246ecfe@paperstreet.colino.net>


On Mon, 2008-03-10 at 08:46 +0100, Colin Leroy wrote:
> On Mon, 10 Mar 2008 01:04:33 +0100, Roel Kluin wrote:
> 
> Hi,
> 
> > logical-bitwise & confusion
> 
> Looks good to me, but I'm not really maintaining that anymore :-)
> I'm not sure who does, Cc:ing Benjamin as he'll probably know.

Nobody is U suspect...

Send it to the list linuxppc-dev@ozlabs.org, it should be picked up
anyway.

Ben.

> > Signed-off-by: Roel Kluin <12o3l@tiscali.nl>
> > ---
> > diff --git a/drivers/hwmon/adt7473.c b/drivers/hwmon/adt7473.c
> > index 9587869..8ea7da2 100644
> > --- a/drivers/hwmon/adt7473.c
> > +++ b/drivers/hwmon/adt7473.c
> > @@ -570,7 +570,7 @@ static ssize_t set_max_duty_at_crit(struct device
> > *dev, struct i2c_client *client = to_i2c_client(dev);
> >  	struct adt7473_data *data = i2c_get_clientdata(client);
> >  	int temp = simple_strtol(buf, NULL, 10);
> > -	temp = temp && 0xFF;
> > +	temp &= 0xFF;
> >  
> >  	mutex_lock(&data->lock);
> >  	data->max_duty_at_overheat = temp;
> > 
> 


  reply	other threads:[~2008-03-10  8:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10  0:04 ADT746X: logical-bitwise & confusion in set_max_duty_at_crit() Roel Kluin
2008-03-10  7:46 ` Colin Leroy
2008-03-10  8:06   ` Benjamin Herrenschmidt [this message]
2008-03-10  8:22     ` Roel Kluin
2008-03-10  9:13       ` Segher Boessenkool
2008-03-10  9:59         ` Roel Kluin
2008-03-10 18:13           ` Darrick J. Wong
2008-03-10 21:17         ` Roel Kluin
2008-03-10 21:56           ` Segher Boessenkool
2008-03-10 22:15             ` Roel Kluin

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=1205136413.8621.3.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=12o3l@tiscali.nl \
    --cc=colin@colino.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox