public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Valentin Schneider <valentin.schneider@arm.com>
To: Peter Zijlstra <peterz@infradead.org>, Wen Yang <wen.yang99@zte.com.cn>
Cc: Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org, zhong.weidong@zte.com.cn,
	Patrick Bellasi <Patrick.Bellasi@arm.com>
Subject: Re: [PATCH] sched/fair: Fix assignment of boolean variables
Date: Mon, 3 Dec 2018 10:03:26 +0000	[thread overview]
Message-ID: <c586c0cb-d867-4b01-e8d0-eea65b1b62ba@arm.com> (raw)
In-Reply-To: <20181203083329.GG11614@hirez.programming.kicks-ass.net>

On 03/12/2018 08:33, Peter Zijlstra wrote:
> On Sat, Dec 01, 2018 at 05:09:36PM +0800, Wen Yang wrote:
>> Fix the following warnings reported by coccinelle:
>> kernel//sched/fair.c:7958:3-12: WARNING: Assignment of bool to 0/1
>>

Duh, Patrick raised that one to me last week but I got caught up in other
things. I realized I could keep the local 'overload' as bool in

    575638d1047e ("sched/core: Change root_domain->overload type to int")

but probably forgot to update 

    757ffdd705ee ("sched/fair: Set rq->rd->overload when misfit")

accordingly.

>> This also makes the code more readable.
> 
> I disagree; anybody that has trouble with 0/1 vs false/true needs to
> stay away from C.
> 
>> Signed-off-by: Wen Yang <wen.yang99@zte.com.cn>
>> CC: Ingo Molnar <mingo@redhat.com>
>> CC: Peter Zijlstra <peterz@infradead.org>
>> CC: linux-kernel@vger.kernel.org
>> ---
>>  kernel/sched/fair.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
>> index a2e8160968cb..f19aa66f9b15 100644
>> --- a/kernel/sched/fair.c
>> +++ b/kernel/sched/fair.c
>> @@ -7955,7 +7955,7 @@ static inline void update_sg_lb_stats(struct lb_env *env,
>>  		if (env->sd->flags & SD_ASYM_CPUCAPACITY &&
>>  		    sgs->group_misfit_task_load < rq->misfit_task_load) {
>>  			sgs->group_misfit_task_load = rq->misfit_task_load;
>> -			*overload = 1;
>> +			*overload = true;
>>  		}
>>  	}
>>  
> 
> Anyway, this code is going away anyway:
> 
>   https://lkml.kernel.org/r/20181119141857.8625-12-quentin.perret@arm.com
> 

      reply	other threads:[~2018-12-03 10:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-01  9:09 [PATCH] sched/fair: Fix assignment of boolean variables Wen Yang
2018-12-01 21:32 ` Joey Pabalinas
2018-12-03  8:33 ` Peter Zijlstra
2018-12-03 10:03   ` Valentin Schneider [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=c586c0cb-d867-4b01-e8d0-eea65b1b62ba@arm.com \
    --to=valentin.schneider@arm.com \
    --cc=Patrick.Bellasi@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=wen.yang99@zte.com.cn \
    --cc=zhong.weidong@zte.com.cn \
    /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