All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] markers: fix sparse warnings in markers.c
Date: Thu, 21 Feb 2008 06:38:34 -0500	[thread overview]
Message-ID: <20080221113834.GA13150@Krystal> (raw)
In-Reply-To: <1203578514.20345.2.camel@brick>

* Harvey Harrison (harvey.harrison@gmail.com) wrote:
> char can be unsigned
> kernel/marker.c:64:20: error: dubious one-bit signed bitfield
> kernel/marker.c:65:14: error: dubious one-bit signed bitfield
> 
> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>

Yep, it makes sense.

Thanks!

Acked-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>

> ---
> Introduced between -rc1 and -rc2
>  kernel/marker.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/marker.c b/kernel/marker.c
> index c4c2cd8..50effc0 100644
> --- a/kernel/marker.c
> +++ b/kernel/marker.c
> @@ -61,8 +61,8 @@ struct marker_entry {
>  	int refcount;	/* Number of times armed. 0 if disarmed. */
>  	struct rcu_head rcu;
>  	void *oldptr;
> -	char rcu_pending:1;
> -	char ptype:1;
> +	unsigned char rcu_pending:1;
> +	unsigned char ptype:1;
>  	char name[0];	/* Contains name'\0'format'\0' */
>  };
>  
> -- 
> 1.5.4.2.200.g99e75
> 
> 
> 

-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

      reply	other threads:[~2008-02-21 11:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21  7:21 [PATCH] markers: fix sparse warnings in markers.c Harvey Harrison
2008-02-21 11:38 ` Mathieu Desnoyers [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=20080221113834.GA13150@Krystal \
    --to=mathieu.desnoyers@polymtl.ca \
    --cc=harvey.harrison@gmail.com \
    --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 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.