lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180130160244.p24of44jgib3botq@art_vandelay>
Date:   Tue, 30 Jan 2018 11:02:44 -0500
From:   Sean Paul <seanpaul@...omium.org>
To:     Ville Syrjälä <ville.syrjala@...ux.intel.com>
Cc:     Sean Paul <seanpaul@...omium.org>,
        "Gustavo A. R. Silva" <gustavo@...eddedor.com>,
        David Airlie <airlied@...ux.ie>, linux-kernel@...r.kernel.org,
        dri-devel@...ts.freedesktop.org,
        Daniel Vetter <daniel.vetter@...el.com>,
        "Gustavo A. R. Silva" <garsilva@...eddedor.com>
Subject: Re: [PATCH v2] drm/edid: use true and false for boolean values

On Tue, Jan 30, 2018 at 05:19:46PM +0200, Ville Syrjälä wrote:
> On Tue, Jan 30, 2018 at 10:09:27AM -0500, Sean Paul wrote:
> > On Tue, Jan 30, 2018 at 04:05:28AM -0600, Gustavo A. R. Silva wrote:
> > > Assign true or false to boolean variables instead of an integer value.
> > > 
> > > This issue was detected with the help of Coccinelle.
> > 
> > I suppose you could also fix up the other preferred assignment by adding !!
> > to the bitwise & operation.
> 
> Assigning >1 to a bool is well defined. No need to clutter the code with
> !! imo.

There are examples of both in the file already. I don't have strong feelings
either way.

Sea

> 
> > 
> > It's also helpful to post the spatch in the commit message so others can
> > replicate your result (this case is pretty trivial, so less important).
> > 
> > Sean
> > 
> > > 
> > > Signed-off-by: Gustavo A. R. Silva <gustavo@...eddedor.com>
> > > ---
> > > Changes in v2:
> > >  - Use true for boolean value in add_detailed_mode as suggested by Daniel
> > >    Vetter.
> > >  - Update subject.
> > > 
> > >  drivers/gpu/drm/drm_edid.c | 4 ++--
> > >  1 file changed, 2 insertions(+), 2 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> > > index ddd5379..b1cb262 100644
> > > --- a/drivers/gpu/drm/drm_edid.c
> > > +++ b/drivers/gpu/drm/drm_edid.c
> > > @@ -2767,7 +2767,7 @@ do_detailed_mode(struct detailed_timing *timing, void *c)
> > >  
> > >  		drm_mode_probed_add(closure->connector, newmode);
> > >  		closure->modes++;
> > > -		closure->preferred = 0;
> > > +		closure->preferred = false;
> > >  	}
> > >  }
> > >  
> > > @@ -2784,7 +2784,7 @@ add_detailed_modes(struct drm_connector *connector, struct edid *edid,
> > >  	struct detailed_mode_closure closure = {
> > >  		.connector = connector,
> > >  		.edid = edid,
> > > -		.preferred = 1,
> > > +		.preferred = true,
> > >  		.quirks = quirks,
> > >  	};
> > >  
> > > -- 
> > > 2.7.4
> > > 
> > 
> > -- 
> > Sean Paul, Software Engineer, Google / Chromium OS
> > _______________________________________________
> > dri-devel mailing list
> > dri-devel@...ts.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/dri-devel
> 
> -- 
> Ville Syrjälä
> Intel OTC

-- 
Sean Paul, Software Engineer, Google / Chromium OS

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ