From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>
Subject: [GIT PULL] fix test cases on 32bit
Date: Sat, 1 Apr 2017 12:32:23 +0200 [thread overview]
Message-ID: <20170401103222.sqqfrshnjya3tkbh@macpro.local> (raw)
In-Reply-To: <20170327141918.61151-1-luc.vanoostenryck@gmail.com>
This series is available at:
git://github.com/lucvoo/sparse.git fix-32bit-tests
based on commit:
97ebb345943918a0688b62cbc9bf878de01ccba4 (sparse-next-2017-03-07)
up to commit:
c1a53a868ebafd1d134e4a77c86074b9d07e4281
-- Luc Van Oostenryck
prev parent reply other threads:[~2017-04-01 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 14:19 [PATCH 0/5] fix test cases on 32bit Luc Van Oostenryck
2017-03-27 14:19 ` [PATCH 1/5] fix test for cast to bool on 32bit machines Luc Van Oostenryck
2017-03-27 14:19 ` [PATCH 2/5] predefine __INT_MAX__ and friends Luc Van Oostenryck
2017-03-27 14:19 ` [PATCH 3/5] predefine __SIZEOF_INT__ & friends Luc Van Oostenryck
2017-03-27 14:19 ` [PATCH 4/5] fix test validation/div.c Luc Van Oostenryck
2017-03-27 14:19 ` [PATCH 5/5] do not depends on limits.h to test __CHAR_BIT__ Luc Van Oostenryck
2017-04-01 10:32 ` Luc Van Oostenryck [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=20170401103222.sqqfrshnjya3tkbh@macpro.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--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).