linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Li <sparse@chrisli.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [GIT PULL] llvm fixes
Date: Mon, 30 Oct 2017 07:13:20 +0800	[thread overview]
Message-ID: <CANeU7Qnu7h09YHhGVOY3r4M9FNOvOrs+kB_yJT-i0cSeLtKhAw@mail.gmail.com> (raw)
In-Reply-To: <20170918095135.12066-1-luc.vanoostenryck@gmail.com>

On Mon, Sep 18, 2017 at 5:51 PM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> Chris,
>
> Please, pull these patches for master.
>
> No surprises here, it's just all March's good old fixes
> for sparse-llvm which have been rebased on top of rc5.
>

Hi Luc,

Sorry for the delay. I will start to reply to your patch email in this series.
I have some feed back store on my computer a while back but I haven't
have to the chance send out the email.

Over all the the series seems good. It seems have some measurable
speed up in my stress test. There is one of two patch I will comment more
in the follow up email. I will reply in the order of the patch send
out. If a patch
does not have comment, that means it looks good to me.

BTW, I think a lot of the 68 patches can be break into smaller series.
There is some inter dependency but not that much especially relate to
the testsuite. Smaller series will make it easier to review.

More email to follow up.

Thanks for the series and sorry for the delay.

Chris

  parent reply	other threads:[~2017-10-29 23:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18  9:51 [GIT PULL] llvm fixes Luc Van Oostenryck
2017-10-02 19:49 ` Luc Van Oostenryck
2017-10-16 14:41 ` Luc Van Oostenryck
2017-10-29 23:13 ` Christopher Li [this message]
2017-11-05  8:29   ` Christopher Li
2017-11-05 17:10     ` Luc Van Oostenryck
2017-11-05 23:18       ` Christopher Li
2017-11-12  1:04         ` Christopher Li
2017-11-12  5:05           ` Luc Van Oostenryck
2017-11-12 10:10             ` Christopher Li
2017-11-12  5:45           ` Luc Van Oostenryck
2017-11-05  8:49   ` Christopher Li
2017-11-05 17:03     ` Luc Van Oostenryck
2017-10-29 23:31 ` Christopher Li
2017-10-30  6:14   ` Luc Van Oostenryck
2017-11-17  9:51 ` Luc Van Oostenryck
     [not found]   ` <CANeU7QnTtcKP9ukNqGmMzfVMviYwYEfYFhgLRHHGxCqR7sPGEQ@mail.gmail.com>
2017-11-17 19:50     ` Luc Van Oostenryck
2017-11-26 17:42       ` Christopher Li
2017-11-26 19:34         ` 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=CANeU7Qnu7h09YHhGVOY3r4M9FNOvOrs+kB_yJT-i0cSeLtKhAw@mail.gmail.com \
    --to=sparse@chrisli.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    /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).