From: Christopher Li <sparse@chrisli.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH 0/3] kill dead loads
Date: Fri, 9 Jun 2017 00:46:52 -0700 [thread overview]
Message-ID: <CANeU7QkMjuc2rvT+ervdFmFOCSSzZHg7Y+h-5TX=zf+XF-pw=g@mail.gmail.com> (raw)
In-Reply-To: <20170608073927.55218-1-luc.vanoostenryck@gmail.com>
On Thu, Jun 8, 2017 at 12:39 AM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> The goal of this series is to eliminate dead loads which,
> especially the deadborn ones which, until now, weren't
> removed.
>
> This series is also available in the git repository at:
> git://github.com/lucvoo/sparse.git kill-dead-loads
This 3 patch looks good to me.
Thanks,
Chris
prev parent reply other threads:[~2017-06-09 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 7:39 [PATCH 0/3] kill dead loads Luc Van Oostenryck
2017-06-08 7:39 ` [PATCH 1/3] extract has_users() from dead_insn() Luc Van Oostenryck
2017-06-08 7:39 ` [PATCH 2/3] let kill_instruction() report if it made some changes or not Luc Van Oostenryck
2017-06-08 7:39 ` [PATCH 3/3] kill dead loads Luc Van Oostenryck
2017-06-09 7:46 ` Christopher Li [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='CANeU7QkMjuc2rvT+ervdFmFOCSSzZHg7Y+h-5TX=zf+XF-pw=g@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).