All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christos Gkekas <chris.gekas@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Nick Dyer <nick@shmanahar.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: atmel_mxt_ts - Remove unnecessary byte_offset check
Date: Mon, 9 Oct 2017 22:06:53 +0100	[thread overview]
Message-ID: <20171009210653.GB2839@inspiron> (raw)
In-Reply-To: <20171009173855.GA19253@dtor-ws>

On 09/10/17 10:38:55 -0700, Dmitry Torokhov wrote:
> On Sun, Oct 08, 2017 at 08:41:16PM +0100, Nick Dyer wrote:
> > On Sun, Oct 08, 2017 at 07:44:18PM +0100, Christos Gkekas wrote:
> > > Variable byte_offset is unsigned so checking whether it is greater or
> > > equal to zero is redundant.
> > > 
> > > Signed-off-by: Christos Gkekas <chris.gekas@gmail.com>
> > 
> > Yep - looks sensible to me.
> > 
> > Signed-off-by: Nick Dyer <nick@shmanahar.org>
> 
> I believe this has been discussed before and Linus told us to keep the
> such checks as is: they neatly document the ranges of values, safe in
> case we ever change the type of the variables, and do not cost us
> anything at execution time.
> 

Fair enough, thanks for your feedback.

I believe you are referring to this:
https://lkml.org/lkml/2006/11/28/206

Regards,
Christos

> 
> > 
> > > ---
> > >  drivers/input/touchscreen/atmel_mxt_ts.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c b/drivers/input/touchscreen/atmel_mxt_ts.c
> > > index 7659bc4..baafaed 100644
> > > --- a/drivers/input/touchscreen/atmel_mxt_ts.c
> > > +++ b/drivers/input/touchscreen/atmel_mxt_ts.c
> > > @@ -1356,7 +1356,7 @@ static int mxt_prepare_cfg_mem(struct mxt_data *data,
> > >  
> > >  			byte_offset = reg + i - cfg_start_ofs;
> > >  
> > > -			if (byte_offset >= 0 && byte_offset < config_mem_size) {
> > > +			if (byte_offset < config_mem_size) {
> > >  				*(config_mem + byte_offset) = val;
> > >  			} else {
> > >  				dev_err(dev, "Bad object: reg:%d, T%d, ofs=%d\n",
> > > -- 
> > > 2.7.4
> > > 
> 
> Thanks.
> 
> -- 
> Dmitry

      reply	other threads:[~2017-10-09 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08 18:44 [PATCH] Input: atmel_mxt_ts - Remove unnecessary byte_offset check Christos Gkekas
2017-10-08 19:41 ` Nick Dyer
2017-10-09 17:38   ` Dmitry Torokhov
2017-10-09 21:06     ` Christos Gkekas [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=20171009210653.GB2839@inspiron \
    --to=chris.gekas@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@shmanahar.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.