public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Sean Paul <seanpaul@chromium.org>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	"David Airlie" <airlied@linux.ie>,
	"Gustavo A. R. Silva" <garsilva@embeddedor.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	"Daniel Vetter" <daniel.vetter@intel.com>
Subject: Re: [PATCH v2] drm/edid: use true and false for boolean values
Date: Tue, 30 Jan 2018 17:31:53 +0100	[thread overview]
Message-ID: <20180130163153.GT25930@phenom.ffwll.local> (raw)
In-Reply-To: <20180130160244.p24of44jgib3botq@art_vandelay>

On Tue, Jan 30, 2018 at 11:02:44AM -0500, Sean Paul wrote:
> 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.

Yeah, I applied this one for now, we can do more color choice discussions
with follow ups :-)

Thanks for the patch.
-Daniel

> 
> 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@embeddedor.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@lists.freedesktop.org
> > > https://lists.freedesktop.org/mailman/listinfo/dri-devel
> > 
> > -- 
> > Ville Syrjälä
> > Intel OTC
> 
> -- 
> Sean Paul, Software Engineer, Google / Chromium OS
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

      reply	other threads:[~2018-01-30 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30 10:05 [PATCH v2] drm/edid: use true and false for boolean values Gustavo A. R. Silva
2018-01-30 15:09 ` Sean Paul
2018-01-30 15:19   ` Ville Syrjälä
2018-01-30 15:31     ` Jani Nikula
2018-01-30 16:02     ` Sean Paul
2018-01-30 16:31       ` Daniel Vetter [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=20180130163153.GT25930@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=garsilva@embeddedor.com \
    --cc=gustavo@embeddedor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seanpaul@chromium.org \
    --cc=ville.syrjala@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox