From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Aurélien Aptel" <aaptel@suse.com>
Cc: linux-sparse@vger.kernel.org
Subject: Re: check idea: warn when mixing signedness in ?: operator (got bitten by this recently)
Date: Wed, 21 Apr 2021 16:46:18 +0300 [thread overview]
Message-ID: <20210421134618.GJ1959@kadam> (raw)
In-Reply-To: <87eef3zrbs.fsf@suse.com>
On Wed, Apr 21, 2021 at 03:43:03PM +0200, Aurélien Aptel wrote:
> Dan Carpenter <dan.carpenter@oracle.com> writes:
> > Yeah. It finds it. :) It works pretty well. The temptation is to
> > ignore left shifts. Otherwise I think I will just push this.
>
> Great, glad to hear! I didn't check everything but these ones look like
> real bugs (samples but still):
>
Yeah. They mostly are real bugs. I'm going to send fixes for
everything tomorrow.
regards,
dan carpenter
prev parent reply other threads:[~2021-04-21 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 10:21 check idea: warn when mixing signedness in ?: operator (got bitten by this recently) Aurélien Aptel
2021-04-19 22:00 ` Luc Van Oostenryck
2021-04-20 12:16 ` Dan Carpenter
2021-04-20 12:44 ` Aurélien Aptel
2021-04-21 10:30 ` Dan Carpenter
2021-04-21 13:43 ` Aurélien Aptel
2021-04-21 13:46 ` Dan Carpenter [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=20210421134618.GJ1959@kadam \
--to=dan.carpenter@oracle.com \
--cc=aaptel@suse.com \
--cc=linux-sparse@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).