From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Dibyendu Majumdar <mobile@majumdar.org.uk>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: sparse-llvm test cases
Date: Fri, 11 Aug 2017 00:41:14 +0200 [thread overview]
Message-ID: <CAExDi1R33RtEh0FU+_dTsrubBuAjjP7vPWJy1-H93fxiVQnhGw@mail.gmail.com> (raw)
In-Reply-To: <CANeU7QmFK3oK9iPcayvQphEWG+rBGn6uQoMeemAq3pJ7JV0AUw@mail.gmail.com>
On Thu, Aug 10, 2017 at 8:01 PM, Christopher Li <sparse@chrisli.org> wrote:
> On Sun, Mar 12, 2017 at 9:13 PM, Dibyendu Majumdar wrote:
>
> For those test case. I think it is very welcome to integrate into sparse.
Sure. Very welcome.
> If you want, you can break them down to smaller, digestible piece
> and start submitting to sparse as patch series for review, or git pull
> request. It will not get pull into this release v0.5.1 for sure. We can
> start the discussion now. I can even have a post release branch doing
> the merges for the patches after the release.
>
>> These are not exactly in the format currently used for testing sparse.
>> It will be nice however to add all the test cases to the official
>> sparse repository.
>
> That is fine. If it is all just test cases, that is relative safe.
> Luc has a hue pile of pending patches I want to merge. If you touch
> some of those core components, which result in Luc need to fix up
> his repository a lot, then I would say hold a little bit for Luc's patches
> being merged. The test case should be more or less fine.
Yes, in no ways should additional test cases be a problem.
-- Luc
next prev parent reply other threads:[~2017-08-10 22:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 1:13 sparse-llvm test cases Dibyendu Majumdar
2017-08-10 18:01 ` Christopher Li
2017-08-10 22:41 ` Luc Van Oostenryck [this message]
2017-08-10 18:38 ` Christopher Li
2017-08-10 20:44 ` Dibyendu Majumdar
2017-08-10 20:59 ` Christopher Li
2017-08-12 13:46 ` Dibyendu Majumdar
2017-08-12 13:59 ` Christopher Li
2017-08-10 22:50 ` Luc Van Oostenryck
2017-08-10 23:55 ` Christopher Li
2017-08-12 13:44 ` Dibyendu Majumdar
2017-08-12 14:43 ` 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=CAExDi1R33RtEh0FU+_dTsrubBuAjjP7vPWJy1-H93fxiVQnhGw@mail.gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=mobile@majumdar.org.uk \
--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).