From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC] CSE: relax type checking in hashing/compare
Date: Mon, 27 Feb 2017 10:40:13 +0100 [thread overview]
Message-ID: <20170227094013.pevbixjonnebaaxa@macbook.local> (raw)
In-Reply-To: <CANeU7Q=Uv0Xb=9PvpSdeoe4epMD0d5UTHED+xx2N7e7XmDkY9w@mail.gmail.com>
On Mon, Feb 27, 2017 at 04:11:44PM +0800, Christopher Li wrote:
> On Fri, Feb 17, 2017 at 8:06 AM, Luc Van Oostenryck
> <luc.vanoostenryck@gmail.com> wrote:
> > I'm missing something?
> >
> > If not, then the following simple patch should be correct.
>
> This patch is missing a S-O-B. Can you add one?
I did this purposely because it was a RFC.
Also:
- I still have some doubts about this patch
- It won't solve anything, only allow more CSE (but maybe more than
really wanted)
- There is no urgency at all.
So I think it would be better to not include it in the coming release
and instead let it ripe a little bit.
But if you really prefer to include it, maybe not in a release but
in another branch, it's fine for me also.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
next prev parent reply other threads:[~2017-02-27 9:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 0:06 [RFC] CSE: relax type checking in hashing/compare Luc Van Oostenryck
2017-02-17 0:06 ` [RFC,original PATCH] CSE: let equivalent cast hash & compare identically Luc Van Oostenryck
2017-02-27 8:09 ` [RFC] CSE: relax type checking in hashing/compare Christopher Li
2017-02-27 8:11 ` Christopher Li
2017-02-27 9:40 ` Luc Van Oostenryck [this message]
2017-04-19 0:32 ` Christopher Li
2017-04-19 16:32 ` Luc Van Oostenryck
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=20170227094013.pevbixjonnebaaxa@macbook.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=torvalds@linux-foundation.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).