From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: CGEL <cgel.zte@gmail.com>, Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
linux-kernel@vger.kernel.org,
Jing Yangyang <jing.yangyang@zte.com.cn>,
Zeal Robot <zealci@zte.com.cn>
Subject: Re: [PATCH linux-next] kernel:fair: fix boolreturn.cocci warnings
Date: Tue, 24 Aug 2021 16:43:03 +0200 [thread overview]
Message-ID: <YSUFdxEZahuIuzB4@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210824094244.2a7ebe0f@oasis.local.home>
On Tue, Aug 24, 2021 at 09:42:44AM -0400, Steven Rostedt wrote:
> On Tue, 24 Aug 2021 09:41:28 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > Doesn't hurt to just take the patch and then you wont have to spend
> > time on new robots flagging this as a "bug".
>
> Or if you don't want to give credit to theses silly robots, just go
> through the code yourself, and make one big cleanup. It's really
> trivial work.
I fundamentally disagree with the patches. 0 is a perfectly fine
spelling of false. And if they'd spend half a minute using google, I'm
sure they would have found me proclaiming as such.
Why should I waste time on people that can't be arsed to do their
homework?
prev parent reply other threads:[~2021-08-24 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 6:23 [PATCH linux-next] kernel:fair: fix boolreturn.cocci warnings CGEL
2021-08-24 8:15 ` Peter Zijlstra
2021-08-24 8:22 ` Peter Zijlstra
2021-08-24 13:41 ` Steven Rostedt
2021-08-24 13:42 ` Steven Rostedt
2021-08-24 14:43 ` Peter Zijlstra [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=YSUFdxEZahuIuzB4@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=cgel.zte@gmail.com \
--cc=dietmar.eggemann@arm.com \
--cc=jing.yangyang@zte.com.cn \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=zealci@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 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.