From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: Christopher Li <sparse@chrisli.org>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [RFC] sparse SSA construction
Date: Tue, 15 Aug 2017 15:06:00 +0100 [thread overview]
Message-ID: <CACXZuxeGgFmjDosHv-Exd9qRLfonFGUrD7sx-ucQejuR0jsD+w@mail.gmail.com> (raw)
In-Reply-To: <CANeU7Qk9C-78+-a2TOGUWiLof9S_p9vO6bHyNf6xZqZ5X1CoUQ@mail.gmail.com>
Hi Chris,
On 15 August 2017 at 14:59, Christopher Li <sparse@chrisli.org> wrote:
> This ssa conversion will need to break into smaller piece for review
> and merge. The general recommended number of patch for the first
> round is 15 or so at a time in the Linux kernel submmitting-patches.rst
> documentation.
>
The good news is that the minimal patch is quite small. I was
surprised by how small it is.
Regards
Dibyendu
next prev parent reply other threads:[~2017-08-15 14:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 20:26 [RFC] sparse SSA construction Luc Van Oostenryck
2017-08-06 23:01 ` Christopher Li
2017-08-06 23:44 ` Luc Van Oostenryck
2017-08-07 0:33 ` Christopher Li
2017-08-07 1:21 ` Luc Van Oostenryck
2017-08-07 1:44 ` Christopher Li
2017-08-15 13:41 ` Dibyendu Majumdar
2017-08-15 13:59 ` Christopher Li
2017-08-15 14:06 ` Dibyendu Majumdar [this message]
2017-08-15 14:07 ` Christopher Li
2017-08-15 14:09 ` Dibyendu Majumdar
2017-08-15 14:18 ` Christopher Li
2017-08-15 18:36 ` Linus Torvalds
2017-08-15 20:14 ` Luc Van Oostenryck
2017-08-15 20:43 ` Linus Torvalds
2017-08-15 21:43 ` Luc Van Oostenryck
2017-08-15 22:44 ` Dibyendu Majumdar
2017-08-16 5:36 ` Christopher Li
2017-08-16 5:15 ` Christopher Li
2017-08-16 4:23 ` Christopher Li
2017-08-16 4:58 ` Christopher Li
2017-08-16 10:40 ` Dibyendu Majumdar
2017-08-16 13:17 ` Christopher Li
2017-08-16 6:41 ` Luc Van Oostenryck
2017-08-16 11:02 ` Dibyendu Majumdar
2017-08-16 12:00 ` Luc Van Oostenryck
2017-08-16 12:16 ` Dibyendu Majumdar
2017-08-16 12:23 ` Christopher Li
2017-08-16 12:28 ` Luc Van Oostenryck
2017-08-16 12:39 ` Dibyendu Majumdar
2017-08-16 12:50 ` Christopher Li
2017-08-16 12:57 ` Dibyendu Majumdar
2017-08-16 13:11 ` Christopher Li
2017-08-16 13:22 ` Christopher Li
2017-08-16 12:17 ` Christopher Li
2017-08-15 20:37 ` 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=CACXZuxeGgFmjDosHv-Exd9qRLfonFGUrD7sx-ucQejuR0jsD+w@mail.gmail.com \
--to=mobile@majumdar.org.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=sparse@chrisli.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).